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/test)<a href="https://agentmods.dev/commands/agricidaniel/claude-code-essentials-vs-code/test"><img src="https://agentmods.dev/badge/commands/agricidaniel/claude-code-essentials-vs-code/test/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/test"><img src="https://agentmods.dev/badge/commands/agricidaniel/claude-code-essentials-vs-code/test.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.00008 | $0.00179 |
| Opus 5.5 | $0.00003 | $0.00072 |
| Sonnet 5.5 | $0.00002 | $0.00036 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
test 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
Generate comprehensive tests for: $ARGUMENTS
Requirements:
- Unit Tests: Test each function in isolation
- Edge Cases: Empty inputs, null values, boundary conditions
- Error Scenarios: Invalid inputs, network failures, timeouts
- Integration Tests: If the code interacts with other modules
Follow these patterns:
- Use the existing test framework in the project
- Match the project's test file naming convention
- Use descriptive test names: "should [expected behavior] when [condition]"
- Group related tests with describe blocks
- Use proper mocking for external dependencies
- Aim for high coverage but prioritize meaningful tests
After generating:
- Run the tests to verify they pass
- Check coverage if available
- Suggest any additional test cases
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 First seen · 24 lines · 8 tokens per session scan A b073777423d7
test is a command published in the GitHub repository AgriciDaniel/claude-code-essentials-vs-code (64 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 179 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
cloudflare-workers:test-setup
Interactive Vitest setup wizard for Cloudflare Workers testing. Configures @cloudflare/vitest-pool-workers, mocks bindings, and creates example tests.
ace:verify-work
User acceptance testing for completed work.
ace:plan-fix
Plan fixes for UAT issues.
session
Complete guide to managing pair programming sessions.
test-tdd
Run when user calls /test-tdd. Scans modified files, locates their corresponding unit/integration test suites, and runs them.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.