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/iml1s/agent-cli-skills/claude-cli-agentnpx skills add ImL1s/agent-cli-skills --skill claude-cli-agentgit clone --depth 1 https://github.com/ImL1s/agent-cli-skillsWrote 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/iml1s/agent-cli-skills/claude-cli-agent)<a href="https://agentmods.dev/skills/iml1s/agent-cli-skills/claude-cli-agent"><img src="https://agentmods.dev/badge/skills/iml1s/agent-cli-skills/claude-cli-agent.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 | $0.00099 | $0.00853 |
| Opus 5 | $0.00049 | $0.00426 |
| Sonnet 5 | $0.00020 | $0.00171 |
| Haiku 4.5 | $0.00010 | $0.00085 |
Grade A, and why
claude-cli-agent 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code CLI (claude -p) Executor
When to use
- User wants Claude Code /
claudeas the coding agent - Need ultracode, workflows,
--agents, or worktree isolation from an orchestrator - Read-only second opinions (
-rplan mode)
For cross-CLI councils, pair with multi-cli-spawn.
Wrapper
./claude-exec.sh -C /path/to/repo "Implement X; stop when done."
./claude-exec.sh -r -C /path/to/repo "Second opinion on this design"
./claude-exec.sh -T -C /path/to/repo "Large audit — use ultracode workflows"
./claude-exec.sh -e high -m sonnet -o json -f /tmp/bundle.txt
./claude-exec.sh -w task-branch --agents '{"reviewer":{"description":"Reviews","prompt":"You review code"}}' "…"
Flags: -m · -t · -C · -o text|json|stream-json · -f · -r (plan mode) ·
-T/--ultracode → --effort ultracode + multi-agent preamble · -P permission-mode ·
-e effort · -w worktree · --agents JSON · --allowed-tools · --disallowed-tools ·
--add-dir · --system-prompt · --append-system-prompt · --mcp-config ·
--strict-mcp-config · --bare · --ask-permissions · --no-git · -- passthrough.
Default executor uses --dangerously-skip-permissions. Setting -P or -r clears that skip.
Prefer capturing stdout for reports. -C is absolutized before use.
Native multi-agent / ultracode
| Mechanism | What it is | How to enable |
|---|---|---|
| Dynamic workflows | JS orchestration script fans out many subagents | Ask for a workflow, or keyword ultracode |
| ultracode | Session policy: xhigh effort + auto-workflow for substantive tasks | -T / --effort ultracode / interactive /effort ultracode |
--agents JSON |
Custom agent definitions for the session | --agents '{...}' |
claude agents |
Manage background agents | Separate subcommand |
| Agent teams | Small peer set that renegotiates live | Product feature; see Claude Code docs |
--worktree |
Isolated git worktree for the session | -w [name] |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 61 lines · 99 tokens per session scan A a157e3019813
claude-cli-agent is a skill published in the GitHub repository ImL1s/agent-cli-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 99 tokens to every session and 853 once invoked, about $0.0005 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-08-31.
Other skills, from other repositories
search-boost
Multi-engine web search before external API/integration work. Use when verifying versions, SDK signatures, cloud quotas, or comparing libraries. Prefer over built-in searchweb.
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
aria
Designs the data model, API contracts, and structural foundation of the system.
peon-ping-log
Log exercise reps for the Peon Trainer. Use when user says they did pushups, squats, or wants to log reps. Examples - "/peon-ping-log 25 pushups", "/peon-ping-log 30 squats", "log 50 pushups".
agy-delegate
Delegate a coding task to the Google Antigravity CLI (agy) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Antigravity or agy - phrasings like "have Antigravity do X", "delegate this to agy", "run it through agy", or "use…
conductor-implement
Executes the tasks defined in the specified track's plan. Use this to start or continue working on a feature, bug fix, or chore.