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/LandonSchropp/agent-toolkitWrote 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/landonschropp/agent-toolkit/add-tests)<a href="https://agentmods.dev/commands/landonschropp/agent-toolkit/add-tests"><img src="https://agentmods.dev/badge/commands/landonschropp/agent-toolkit/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/landonschropp/agent-toolkit/add-tests"><img src="https://agentmods.dev/badge/commands/landonschropp/agent-toolkit/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.00007 | $0.00179 |
| Opus 5.5 | $0.00003 | $0.00072 |
| Sonnet 5.5 | $0.00001 | $0.00036 |
| Haiku 4.5 | $0.00001 | $0.00018 |
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 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
Ask the user: "What would you like to add tests for?"
After receiving their response, add tests for the user's target using the following process:
-
Invoke the
ls-typescript:testing-typescriptskill. -
Analyze current state: Determine the appropriate test file location. If there's an existing test file, read it to understand the current structure.
-
Plan test structure: List describe and context blocks without wrapping in commands:
functionName when condition A when condition B when edge case C -
Review and approval: Wait for feedback on proposed structure before implementation.
-
Implement Incrementally: Implement one context block at a time. Wait for approval after each context implementation. Run tests after each context addition. Fix failures before proceeding.
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 · 22 lines · 7 tokens per session scan A 4196492b80ee
add-tests is a command published in the GitHub repository LandonSchropp/agent-toolkit (3 stars, last pushed today), licensed MIT. It adds 7 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-31.
Other commands, from other repositories
speckit.verify
Validates implementation completion by checking tasks, logic, tests, and code quality against specifications. Use when you need to verify that all tasks are properly completed.
devkit.java.write-integration-tests
Generates comprehensive integration tests for Spring Boot classes using Testcontainers (PostgreSQL, Redis, MongoDB) with @ServiceConnection pattern. Use when writing integration tests for service or repository classes.
devkit.java.write-unit-tests
Generates comprehensive JUnit 5 unit tests for Java classes with Mockito mocking and AssertJ assertions. Use when writing unit tests for service, controller, or utility classes.
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
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.