X-CMD is a POSIX-shell toolkit that provides reusable shell modules and on-demand command-line packages for bash, zsh, ash, and dash. It is designed for people and AI agents that need shell utilities, integrations, and agent-related workflows, and the catalogue contains a large collection of skills for using it.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/x-cmd/x-cmd/loopnpx skills add x-cmd/x-cmd --skill loopgit clone --depth 1 https://github.com/x-cmd/x-cmdWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/x-cmd/x-cmd/loop)<a href="https://agentmods.dev/skills/x-cmd/x-cmd/loop"><img src="https://agentmods.dev/badge/skills/x-cmd/x-cmd/loop.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00025 | $0.00394 |
| Opus 5 | $0.00013 | $0.00197 |
| Sonnet 5 | $0.00005 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
loop scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Loop Runner
Trigger
Use when:
- User says
/loop <interval> <prompt> - User wants recurring monitoring or periodic execution
Steps
Step 1: Parse Arguments
/loop <interval> <prompt>
Interval patterns:
| Pattern | Cron Expression |
|---|---|
Nm (N ≤ 59) |
*/N * * * * |
Nh (N ≤ 23) |
0 */N * * * |
Nd |
0 0 */N * * |
Round non-dividing intervals to nearest clean value.
Step 2: Clarify Intent
Ask user:
- What to monitor (parse prompt)
- How to execute (which x-cmd module or command)
- Where to store results
Step 3: Configure Notification
Ask before creating:
- Memory (default) — store for later review
- Mailbox — notification on new results
- Other user-specified method
Step 4: Create Cron Job
x cron add \
--name "loop-$(date +%Y%m%d%H%M%S)" \
--desc "<description>" \
"<cron-expression>" \
"<full-command>"
Step 5: Execute Immediately
Run the command now; do not wait for first cron fire.
Step 6: Confirm
Report to user:
- Job name and cron expression
- Human-readable cadence
- Monitoring target
- Result storage location
- Cancellation:
x cron rm <name>
Constraints
- Always ask about result storage before creating
- Always execute immediately
- Round messy intervals and inform user
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 74 lines · 25 tokens per session scan A eac6df3133f2
loop is a skill published in the GitHub repository x-cmd/x-cmd (4,640 stars, last pushed yesterday), licensed Apache-2.0. It adds 25 tokens to every session and 394 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
warpctrl
Control and inspect the currently running local Warp application with the warpctrl CLI. Use this skill whenever the user asks the agent to manipulate Warp's own windows, tabs, panes, sessions, input buffer, themes, or UI surfaces; open a file in Warp; inspect local Warp state; or explain how to invoke Warp Control…
cross-platform-cloud-verification
Orchestrates cost-conscious cloud verification across available operating-system and architecture runners after cheaper checks pass. Use whenever a code change, bug fix, build, packaging flow, native dependency, UI behavior, filesystem behavior, or test has material cross-platform implications, even if the user only…
change-keybinding
Customize Warp keyboard shortcuts (keybindings, keymappings) by editing the user's keybindings.yaml file. Use when the user asks to remap a key combination, rebind an action, change a shortcut, or remove a default keybinding (e.g. "change ctrl+space to ctrl+s", "rebind the command palette to cmd+p", "remove the…
create-tab-config
Create new Warp tab config TOML files from natural-language requests. Use when the user wants a new tab config, a new tab layout, or asks for a slash command to generate a tab config.
pipedream-workflows
Use when pipedream serverless workflows — triggers, code steps, pre-built actions, data stores, HTTP. Use when working with pipedream workflows.
completion-script-generator
Generates shell completion scripts for CLI tools. Parses command structure from help output, commander/yargs configs, or manual specification. Produces completions for bash, zsh, and fish that follow each shell's conventions.