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/Goldziher/ai-rulezWrote 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/goldziher/ai-rulez/add-test)<a href="https://agentmods.dev/commands/goldziher/ai-rulez/add-test"><img src="https://agentmods.dev/badge/commands/goldziher/ai-rulez/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/goldziher/ai-rulez/add-test"><img src="https://agentmods.dev/badge/commands/goldziher/ai-rulez/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.00008 | $0.00104 |
| Opus 5.5 | $0.00003 | $0.00042 |
| Sonnet 5.5 | $0.00002 | $0.00021 |
| Haiku 4.5 | $0.00001 | $0.00010 |
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 today.
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 test
- Locate
$ARGUMENTSwithgit grep -n "def $ARGUMENTS"and read it. - Write one test for the normal case and one for the main edge case next to the existing tests.
- Run the new tests.
Done when both tests pass. If one fails because of a real bug, report the bug and do not change the function.
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.
- today First seen · 13 lines · 8 tokens per session scan A 219cf7534e02
add-test is a command published in the GitHub repository Goldziher/ai-rulez (163 stars, last pushed yesterday), licensed MIT. It adds 8 tokens to every session and 104 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-10-17.
Other commands, from other repositories
test
A command that runs JavaScript or TypeScript tests with npm or Vitest, a test-runner tool, and explains any failures.
gsd-add-tests
Generate tests for a completed phase based on UAT criteria and implementation.
merge-work-packets
Verify all tracks complete, invoke merging-worktrees, run QA gates, report final integration status.
merge-worktree-execute
Phase 2: Sequential Round Merging - merge worktrees in dependency order with testing after each round.
speckit.spec-stats.runs
On-demand execution — reads verified suite command from .specify/memory/tdd-profile.md, runs it for selected specs (--all, spec id/slug, or default active feature), captures pass/fail + duration + tail, appends run record to .specify/stats/runs.json, refreshes dashboard health column.
merge-worktree-verify
Phases 4-5: Final Verification and Cleanup — run full test suite, verify contracts, clean up worktrees.