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/cyperx84/claude-code-plugin-examples/test-filegit clone --depth 1 https://github.com/cyperx84/claude-code-plugin-examplesWhat 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.00006 | $0.00252 |
| Opus 5 | $0.00003 | $0.00126 |
| Sonnet 5 | $0.00001 | $0.00050 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
test-file 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
Test Specific File
Run tests for the file: $ARGUMENTS
Process:
-
If user provides source file (e.g., @src/utils.ts):
- Find corresponding test file
- If no test file exists, offer to create one using /agent test-generator
-
If user provides test file:
- Run that specific test file
- Show detailed output
-
Run tests:
- Execute with verbose output
- Show each test case result
- Display timing for each test
- Show console logs if available
-
Report results:
- Summary for this file
- Individual test case results
- Any errors or failures with stack traces
- Suggestions for fixing failures
-
Interactive options:
- Watch mode: Re-run on file changes
- Debug mode: Run with debugger attached
- Update snapshots: If snapshot tests
- Generate missing tests: If coverage gaps
Example usage:
/test-file @src/utils/parser.ts/test-file tests/auth.test.ts/test-file UserComponent
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 · 41 lines · 6 tokens per session scan A e2ec4a53e877
test-file is a command published in the GitHub repository cyperx84/claude-code-plugin-examples (2 stars, last pushed 10mo ago), licensed MIT. It adds 6 tokens to every session and 252 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.