Borrowing it
Nothing to install: this file belongs to modeled-information-format/mnemonic. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/modeled-information-format/mnemonic/main/.claude/commands/add-test.mdgit clone --depth 1 https://github.com/modeled-information-format/mnemonicWrote 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/modeled-information-format/mnemonic/add-test)<a href="https://agentmods.dev/commands/modeled-information-format/mnemonic/add-test"><img src="https://agentmods.dev/badge/commands/modeled-information-format/mnemonic/add-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/modeled-information-format/mnemonic/add-test"><img src="https://agentmods.dev/badge/commands/modeled-information-format/mnemonic/add-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.00014 | $0.00834 |
| Opus 5.5 | $0.00006 | $0.00334 |
| Sonnet 5.5 | $0.00003 | $0.00167 |
| Haiku 4.5 | $0.00001 | $0.00083 |
Grade A, and why
add-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.
Copies of this mod
1 near-identical copy found in the catalogue:
- add-test — 91% identical, 63 lines differ
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Test Definition
Interactively create a new test definition and add it to the test suite.
Process
Question 1: Component Type If not provided via argument, ask:
- Command
- Skill
- Agent
- Other
Question 2: Test ID
Ask for a unique test identifier.
Suggest format: category_component_action (e.g., cmd_capture_basic)
Question 3: Description Ask for a human-readable description of what the test validates.
Question 4: Action Ask what Claude should do for this test. Provide examples based on component type:
- Command: "Run the /command-name command"
- Skill: "Ask: 'trigger phrase'"
- Agent: "Launch the agent-name agent with task: 'description'"
Question 5: Expectations Ask what should be validated:
- Text that should appear (contains)
- Text that should NOT appear (not_contains)
- Pattern to match (regex)
Question 6: Variable Capture Ask if any value should be captured for later tests. If yes, ask for variable name and capture pattern.
Question 7: Dependencies Ask if this test depends on another test running first.
Question 8: Tags Ask for tags to categorize the test:
- smoke, critical, regression, slow, etc.
Example output (YAML):
- id: cmd_capture_basic
description: Create a new memory and verify it was captured
category: commands
action: "Run the /mnemonic:capture command with content: 'Test memory'"
expect:
- contains: "captured"
- not_contains: "error"
tags: [smoke, commands]
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 · 145 lines · 14 tokens per session scan A caab4ed9c672
add-test is a command published in the GitHub repository modeled-information-format/mnemonic (23 stars, last pushed 7d ago), licensed MIT. It adds 14 tokens to every session and 834 once invoked, about $0.0001 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
plan-sdd
A command that creates an implementation plan from a written specification using Clean Architecture and TDD. TDD, or test-driven development, means writing tests before the code they check.
design-chain
Run one design round through the design chain: vision, owners, brief with verbatim anchors, three directions, craft manifest, build, measure, critique, proof, checks, readers, seal. Nothing is shown before the seal.
linear-drain
Create the queued Linear projects and issues that shell scripts captured offline.
voice-refresh
Refresh the founder-voice DNA from new Granola meetings (interactive, MCP-backed). Pulls meetings since the last refresh, harvests Assaf-only speech, runs the Stage 2-3 orchestrator, and presents a founder-gated delta. Never auto-writes voice-dna.md.
q-research
Read the research-mode skill's SKILL.md for the full ruleset before proceeding. Follow all constraints, the source lookup cascade, the token budget, and the "what counts as cited" rules exactly.
fleet-sim
Run the fleet week simulator (a simulated week of every machine's real schedule, with injected faults) and compare its breaks with the previous run.