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 commands/anilcancakir/claude-code-plugins/my_auditgit clone --depth 1 https://github.com/anilcancakir/claude-code-pluginsWrote 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/anilcancakir/claude-code-plugins/my_audit)<a href="https://agentmods.dev/commands/anilcancakir/claude-code-plugins/my_audit"><img src="https://agentmods.dev/badge/commands/anilcancakir/claude-code-plugins/my_audit.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.00044 | $0.01779 |
| Opus 5 | $0.00022 | $0.00890 |
| Sonnet 5 | $0.00009 | $0.00356 |
| Haiku 4.5 | $0.00004 | $0.00178 |
Grade A, and why
my_audit scanned grade A with 1 finding 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 3d 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.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat .claude/settings.json 2>/dev/null Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/my_audit - Project Setup Audit
Analyze existing project.md, brand.md, and CLAUDE.md configuration with detailed quality reports and improvement suggestions.
Arguments
- No arguments: Standard report format
--compact: One-line-per-file summary (faster, less tokens)--verbose: Full detailed report with all criteria
Output Formats
Compact Format (--compact)
PROJECT AUDIT SUMMARY
=====================
project.md: [X] Found (72/100 B) | Missing: metrics, audience detail
brand.md: [ ] Missing | Run /my_brand
CLAUDE.md: [X] Found (58/100 D) | Missing: testing, gotchas, brand ref
Grade: C (43/100) | Run: /my_brand, then /my_setup --full
Standard Format (default)
Full tables with scores per criterion, but skip detailed notes unless issues found.
Workflow
Phase 1: Discovery
Find all configuration files:
# Project brief
ls -la project.md PROJECT.md 2>/dev/null
# Brand guidelines
ls -la brand.md BRAND.md 2>/dev/null
# Claude Code configuration
find . -name "CLAUDE.md" -o -name ".claude.md" -o -name ".claude.local.md" 2>/dev/null | head -20
# Check .claude directory
ls -la .claude/ 2>/dev/null
# Check for rules
ls -la .claude/rules/ 2>/dev/null
# Check for settings
cat .claude/settings.json 2>/dev/null
Phase 2: Workflow Status
Check if the recommended workflow was followed:
WORKFLOW STATUS
===============
1. /my_project (project.md)
Status: [Found / Missing]
[If found: Score X/100]
2. /my_brand (brand.md)
Status: [Found / Missing]
[If found: Score X/100]
3. /my_setup (CLAUDE.md)
Status: [Found / Missing]
[If found: Score X/100]
Recommendation:
[If missing files, suggest running the appropriate command]
Phase 3: Project.md Assessment
If project.md exists, evaluate against these criteria:
| Criterion | Weight | What to Check |
|---|---|---|
| Project identity | 20 | Name, tagline, description present? |
| Problem statement | 20 | Pain point clearly defined? |
| Target audience | 15 | User persona described? |
| Value proposition | 15 | Unique value articulated? |
| Features as benefits | 15 | Features focus on user value? |
| Success metrics | 15 | Measurable goals defined? |
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.
- 3d ago First seen · 270 lines · 44 tokens per session scan A 6aa3239f7091
my_audit is a command published in the GitHub repository anilcancakir/claude-code-plugins (6 stars, last pushed 7mo ago), licensed MIT. It adds 44 tokens to every session and 1,779 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
debug
Systematic debugging with hypotheses and evidence gathering.
health
Run the Self-Star Doctor - a green/yellow/red health board across all 7 junctions of the self- loop.
plan-new
Plan a complex project with discovery, structure, and kill criteria.
create-hook
Create a new custom automation hook.
remember
Explicitly save something to memory as an experience.
context-stats
Show context window usage, active tier, and system stats.