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/saeedkolivand/ai-job-hunter-appWrote 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/saeedkolivand/ai-job-hunter-app/add-tests)<a href="https://agentmods.dev/commands/saeedkolivand/ai-job-hunter-app/add-tests"><img src="https://agentmods.dev/badge/commands/saeedkolivand/ai-job-hunter-app/add-tests/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/saeedkolivand/ai-job-hunter-app/add-tests"><img src="https://agentmods.dev/badge/commands/saeedkolivand/ai-job-hunter-app/add-tests.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.00012 | $0.00236 |
| Opus 5 | $0.00006 | $0.00118 |
| Sonnet 5 | $0.00002 | $0.00047 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
add-tests 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 11d 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
Add tests for: $ARGUMENTS (or the current git diff).
- Load
testing-rules+token-efficiency. - Spawn the
test-authorsubagent (Task) — it writes tests (integration→unit→e2e; golden for PDF/DOCX; realistic fixtures over mocks; cover success + failure + error/security paths + edge cases). Reuserenderer/test-support.tsxutilities andsrc-tauri/tests/conventions. - Then spawn
testing-reviewer(Task) to audit coverage of the changed code + test quality (weak assertions, flakiness, over-mocking, redundancy). It NEVER writes tests. - Run the tests (
pnpm test/cargo test); ensure green. Report any HIGH/CRITICAL coverage gap as blocking.
(/add-tests always runs test-author regardless of the testable-logic predicate — tests were explicitly requested.)
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.
- 11d ago First seen · 14 lines · 12 tokens per session scan A 6fc3b8ff90cf
add-tests is a command published in the GitHub repository saeedkolivand/ai-job-hunter-app (54 stars, last pushed today), licensed Apache-2.0. It adds 12 tokens to every session and 236 once invoked, about $0.0001 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
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
boundary-heatmap
Generate a visual heatmap of knowledge boundaries showing safe zones, risk areas, and semantic coverage.
test
Run the project test suite and report results.
cli-review
Review Rust CLI applications for UX, error handling, testing, and cross-platform compatibility.
component-scaffold
You are a React component architecture expert specializing in scaffolding production-ready, accessible, and performant components. Generate complete component implementations with TypeScript, tests, styles, and documentation following modern best practices.
checklist
Generate a custom checklist for the current feature based on user requirements.