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/doncheli/don-cheli-sddWrote 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/doncheli/don-cheli-sdd/auditar)<a href="https://agentmods.dev/commands/doncheli/don-cheli-sdd/auditar"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/auditar.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.00005 | $0.00060 |
| Opus 5 | $0.00003 | $0.00030 |
| Sonnet 5 | $0.00001 | $0.00012 |
| Haiku 4.5 | $0.00001 | $0.00006 |
Grade A, and why
auditar 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.
What it actually says
/dc:auditar
Uso
/dc:auditar [componente]
/dc:auditar todo
Audita la integridad de comandos, habilidades y configuración del framework.
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 · 16 lines · 5 tokens per session scan A 139f383b269c
auditar is a command published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 27d ago), licensed Apache-2.0. It adds 5 tokens to every session and 60 once invoked, about $0.0000 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 commands, from other repositories
forensics
Post-mortem investigation for failed or stuck workflows. Analyzes git history and planning artifacts.
audit-fix
Run audit, prioritize findings, auto-fix via quick tasks, test, and commit.
scan
Analyze an existing codebase. Maps structure, architecture, conventions, and concerns.
debug
Systematic debugging with hypothesis testing. Persistent across sessions.
optimize
Suggest concrete performance improvements for the given file or directory.
fix-issue
A command that takes a GitHub Issue—a tracked bug, request, or question—and guides its fix from investigation through testing and submission. TDD means writing a failing test first, then changing the code until the test passes.