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.
git clone --depth 1 https://github.com/kiliczsh/claude-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/commands/kiliczsh/claude-cmd/template)<a href="https://agentmods.dev/commands/kiliczsh/claude-cmd/template"><img src="https://agentmods.dev/badge/commands/kiliczsh/claude-cmd/template/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/kiliczsh/claude-cmd/template"><img src="https://agentmods.dev/badge/commands/kiliczsh/claude-cmd/template.svg" alt="Reviewed on agentmods" width="80" 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.00010 | $0.00294 |
| Opus 5.5 | $0.00004 | $0.00118 |
| Sonnet 5.5 | $0.00002 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
Command Name 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 1mo 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
Command Name
Brief description of what this command does and its purpose.
Features
- Feature 1: Description
- Feature 2: Description
- Feature 3: Description
Usage
Explain how to use this command:
Basic Usage
Example of basic usage
Advanced Usage
Example of advanced usage with options
Examples
Example 1: Simple Case
Description of what this example does.
Code or command example
Example 2: Complex Case
Description of what this example does.
More complex example
Configuration
If the command requires configuration, explain it here:
- Setting 1: What it does
- Setting 2: What it does
Notes
- Important note 1
- Important note 2
- Any limitations or considerations
Arguments
If this command takes arguments, describe them:
$ARGUMENTS
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.
- 1mo ago First seen · 69 lines · 10 tokens per session scan A 8b7e65eaf20e
Command Name is a command published in the GitHub repository kiliczsh/claude-cmd (315 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 294 once invoked, about $0.0000 per session on Opus 5.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-30.
Other commands, from other repositories
add-performance-monitoring
Setup application performance monitoring.
ci-setup
Setup continuous integration pipeline.
group-chat
Create a multi-agent group chat with AG2 using configurable speaker selection patterns.
new-tool
Create a tool function for an AG2 agent with type annotations, docstrings, and JSON return contracts.
workflow-from-spec
Design a complete multi-agent workflow from a natural language description, selecting the right orchestration pattern.
all-tools
Display all available development tools.