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/AgriciDaniel/claude-code-essentials-vs-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/commands/agricidaniel/claude-code-essentials-vs-code/fix-issue)<a href="https://agentmods.dev/commands/agricidaniel/claude-code-essentials-vs-code/fix-issue"><img src="https://agentmods.dev/badge/commands/agricidaniel/claude-code-essentials-vs-code/fix-issue/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/commands/agricidaniel/claude-code-essentials-vs-code/fix-issue"><img src="https://agentmods.dev/badge/commands/agricidaniel/claude-code-essentials-vs-code/fix-issue.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.00007 | $0.00139 |
| Opus 5.5 | $0.00003 | $0.00056 |
| Sonnet 5.5 | $0.00001 | $0.00028 |
| Haiku 4.5 | $0.00001 | $0.00014 |
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 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.
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
- Summarize the local diff, tests, and any remaining limitations for review
Do not commit, push, or change the issue's status unless the user explicitly requests that action.
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.
- 1mo ago Changed · +3 lines afce84544f8c
- 1mo 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 (64 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 139 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
ace:validate-zones
Check for zone conflicts in project-types.json.
AGENTS
Run the current binary in a temporary test repository with a real PTY. Use tmux-cli when available, capture terminal output, and inspect -vv logs when behavior depends on timing or shell state. Avoid treating a piped command as proof of interactive behavior.
session-report
Generate a Markdown dashboard of recent Claude Code sessions with git activity, commits, and repo tracking.
pr-ready
Run the project's pre-commit review loop to determine whether the current branch is ready to push — lint, tests, parallel pr-review-toolkit agents plus an over-engineering audit, fix-and-re-run until convergence.
deploy
Run the complete ClawBridge release process. This is the ONLY way to deploy — follow every step.
release
Command "release" from getsentry/toolkit, covering examples, list releases (auto-detect org), list releases in a specific org, view release details and create and finalize a release.