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/orlando-japan/claude-code-setting/test-focusedgit clone --depth 1 https://github.com/orlando-japan/claude-code-settingWrote 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/orlando-japan/claude-code-setting/test-focused)<a href="https://agentmods.dev/commands/orlando-japan/claude-code-setting/test-focused"><img src="https://agentmods.dev/badge/commands/orlando-japan/claude-code-setting/test-focused.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.00009 | $0.00347 |
| Opus 5 | $0.00005 | $0.00173 |
| Sonnet 5 | $0.00002 | $0.00069 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
test-focused 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 4d 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
Run a targeted test pass rather than the full suite.
Step 1 — find changed files:
git diff --name-only HEAD
git status --porcelain
Step 2 — map files to tests:
- For each source file, find its co-located test (e.g.,
foo.ts→foo.test.ts,foo.py→test_foo.py). - For files with no direct test, find tests that import them via grep.
- If the change is in shared/core code with many dependents, fall back to the full suite for that module — don't try to be too clever.
Step 3 — run:
Detect the test runner from package.json, pyproject.toml, Cargo.toml, go.mod. Run it with the focused file list.
Step 4 — report:
- Pass/fail summary.
- For failures: copy the actual error, don't paraphrase.
- If a test failed, stop and report — don't try to fix it unless the user asks.
When NOT to use this:
- Right before merging — run the full suite then.
- After a refactor that touches shared types — the blast radius is too wide to predict.
- On a CI failure — reproduce locally with the exact same command CI used.
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.
- 4d ago First seen · 36 lines · 9 tokens per session scan A 22b8832151d3
test-focused is a command published in the GitHub repository orlando-japan/claude-code-setting (2 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 347 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
git
Git operations with intelligent commit messages and workflow optimization.
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.