# Passing arguments using ansible-builtin-command

**URL:** <https://forum.ansible.com/t/passing-arguments-using-ansible-builtin-command/45038>\
**Category:** Get Help\
**Created:** [December 30, 2025, 10:05am UTC](https://forum.ansible.com/t/passing-arguments-using-ansible-builtin-command/45038 "2025-12-30T10:05:39Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![flowerysong](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/flowerysong/32/2305_2.png) [@flowerysong](https://forum.ansible.com/u/flowerysong)\
**Post date:** [December 30, 2025, 5:58pm UTC](https://forum.ansible.com/t/passing-arguments-using-ansible-builtin-command/45038/3 "2025-12-30T17:58:09Z")

</div>

A common issue is that the short form of calling the command and shell modules introduces an additional layer of parsing. It is significantly more robust to use the `cmd` argument, e.g instead of:

```yaml
- command: echo hello world

```

you should write

```yaml
- command:
    cmd: echo hello world

```

It’s slightly more typing, but avoids quite a bit of weirdness.

---

_[View the full topic](https://forum.ansible.com/t/passing-arguments-using-ansible-builtin-command/45038)._