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 skills add fazxes/Claude-code --skill command-developmentgit clone --depth 1 https://github.com/fazxes/Claude-codeWrote 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/fazxes/claude-code/command-development)<a href="https://agentmods.dev/skills/fazxes/claude-code/command-development"><img src="https://agentmods.dev/badge/skills/fazxes/claude-code/command-development/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/skills/fazxes/claude-code/command-development"><img src="https://agentmods.dev/badge/skills/fazxes/claude-code/command-development.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.00099 | $0.04335 |
| Opus 5.5 | $0.00040 | $0.01734 |
| Sonnet 5.5 | $0.00020 | $0.00867 |
| Haiku 4.5 | $0.00010 | $0.00434 |
Grade A, and why
command-development 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
10 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.
- examples/plugin-commands.md 14 KB
- examples/simple-commands.md 8.5 KB
- README.md 7.5 KB
- references/advanced-workflows.md 13 KB
- references/documentation-patterns.md 15 KB
- references/frontmatter-reference.md 8.9 KB
- references/interactive-commands.md 20 KB
- references/marketplace-considerations.md 16 KB
- references/plugin-features-reference.md 14 KB
- references/testing-strategies.md 14 KB
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 · 885 lines · 99 tokens per session scan A c55ad02cfe4c
command-development is a skill published in the GitHub repository fazxes/Claude-code (246 stars, last pushed 6mo ago), with no licence file. It adds 99 tokens to every session and 4,335 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
technical-troubleshooting
Provide setup, troubleshooting, and maintenance guidance. Use when the user reports a device that won't power on, connectivity issues, setup questions, overheating, or maintenance concerns.
implement-comment
Use when operating as the Fabrik Implement comment reviewer. This skill guides applying user-requested code changes during implementation, committing and pushing, and updating the task checklist — without signaling stage completion.
specify-comment
Use when operating as the Fabrik Specify comment reviewer. This skill guides incorporation of user answers into an evolving spec, removing resolved questions and surfacing follow-ups until the spec is complete.
ritual
Discover recurring behaviors from memory and offer to formalize them as scheduled jobs.
trailhead-manage
Skill "trailhead-manage" from ToRvaLDz/trailhead, covering load first, in order and routing: verb to engine.
coding-quality-loop
Use when a coding agent must turn a software goal, bug, issue, or refactor into a small, verified, independently reviewed code change.