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/agricidaniel/claude-code-essentials-vs-code/fix-issuegit clone --depth 1 https://github.com/AgriciDaniel/claude-code-essentials-vs-codeWhat 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.00007 | $0.00121 |
| Opus 5 | $0.00003 | $0.00060 |
| Sonnet 5 | $0.00001 | $0.00024 |
| Haiku 4.5 | $0.00001 | $0.00012 |
Grade A, and why
fix-issue 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 2d 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
Please analyze and fix GitHub issue: $ARGUMENTS
Follow these steps:
- Use
gh issue view $ARGUMENTSto get issue details - Understand the problem described
- Search the codebase for relevant files
- Implement the necessary fix
- Write tests to verify the fix
- Run linter and fix any issues
- Commit with message: "fix: resolve #$ARGUMENTS - [brief description]"
Be thorough and ensure the fix doesn't break existing functionality.
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.
- 2d ago First seen · 16 lines · 7 tokens per session scan A d8810368f88a
fix-issue is a command published in the GitHub repository AgriciDaniel/claude-code-essentials-vs-code (57 stars, last pushed 4mo ago), licensed MIT. It adds 7 tokens to every session and 121 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-08-30.
Other commands, from other repositories
canvas
AI-orchestrated visual canvas production — create, populate, layout, present, generate, and export Obsidian canvases.
ace:execute-plan
Execute current PLAN.md with parallel Team Leads.
ace:validate-zones
Check for zone conflicts in project-types.json.
ace:consider-issues
Review deferred issues for potential inclusion.
ace:validate-plan
Verify PLAN.md structure before execution.
ace:recover-execution
Resume from mid-plan execution failures.