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/juanmhidalgo/claude-plugins/auditgit clone --depth 1 https://github.com/juanmhidalgo/claude-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/juanmhidalgo/claude-plugins/audit)<a href="https://agentmods.dev/commands/juanmhidalgo/claude-plugins/audit"><img src="https://agentmods.dev/badge/commands/juanmhidalgo/claude-plugins/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.00038 | $0.00736 |
| Opus 5 | $0.00019 | $0.00368 |
| Sonnet 5 | $0.00008 | $0.00147 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
audit 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 yesterday.
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
Context
- Branch: !
git branch --show-current - Recent commits: !
git log --oneline -5
<best_practices> @performance/skills/performance-optimization/SKILL.md </best_practices>
Performance Audit Workflow
Audit scope: $ARGUMENTS (if empty, audit the full codebase for anti-patterns).
Rule: NEVER optimize without measurement. Measure → Identify → Fix → Verify → Guard.
Phase 1: Scope & Stack Detection
- Determine audit scope from argument (specific path, endpoint, or full app)
- Detect the stack: frontend (React, Vue, etc.), backend (Node, Python, etc.), or both
- Identify build tools, test frameworks, and available profiling commands
Phase 2: Anti-Pattern Scan
Search the codebase for common performance anti-patterns:
Backend:
- N+1 queries: nested loops with database calls, missing
include/select_related - Unbounded fetches:
findMany()/SELECT *withoutLIMITor pagination - Blocking operations in async contexts
- Missing database indexes for frequently queried columns
Frontend:
- Large bundle: importing entire libraries instead of specific functions
- Missing code splitting: no
lazy()/ dynamicimport() - Unnecessary re-renders: inline object/function creation in JSX
- Images without dimensions, lazy loading, or responsive sources
- Render-blocking CSS/JS in the head
Phase 3: Measurement
Run appropriate profiling tools:
- Frontend: Bundle size analysis, Lighthouse (if available)
- Backend: Query logging, endpoint response times
- Both: Build time, test suite duration
Phase 4: Report
For each finding:
- What: The specific anti-pattern or bottleneck
- Where: File path and line number
- Impact: Estimated performance effect (high/medium/low)
- Fix: Concrete code change with before/after
- Verify: How to measure the improvement
Organize findings by impact (highest first).
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.
- yesterday First seen · 96 lines · 38 tokens per session scan A 6420d934a06f
audit is a command published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 10d ago), licensed MIT. It adds 38 tokens to every session and 736 once invoked, about $0.0002 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
optimize
Optimize code for performance, bundle size, or resource usage.
migrate-example
Migra un ejemplo de Web Worker al dominio neutral y lo renderiza en los 5 themes (pipeline punta a punta con loop de design-review).
hatch3r-benchmark
Run and analyze performance benchmarks. Compare results against baselines, identify regressions, and produce performance reports.
speckit.git.feature
Create a feature branch with sequential or timestamp numbering.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.