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/test-command)<a href="https://agentmods.dev/commands/goldziher/ai-rulez/test-command"><img src="https://agentmods.dev/badge/commands/goldziher/ai-rulez/test-command/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/test-command"><img src="https://agentmods.dev/badge/commands/goldziher/ai-rulez/test-command.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.00010 | $0.00199 |
| Opus 5.5 | $0.00004 | $0.00080 |
| Sonnet 5.5 | $0.00002 | $0.00040 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
test-command 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
Test Command
This is a test command to verify the command generation system works correctly.
Instructions
When this command is invoked:
- Verify the command metadata is properly loaded
- Check that the command appears in the appropriate preset outputs
- Validate that target filtering works correctly
Expected Behavior
The command should be generated as:
- Claude:
.claude/skills/test/SKILL.md - Cursor:
.cursor/rules/cmd-test.mdc
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 Changed · +11 lines · -2 tokens per session 3fe54082dca2
- 16d ago Changed · -1 lines 124c9c731561
- 1mo ago First seen · 31 lines · 12 tokens per session scan A c423c8fe8958
test-command is a command published in the GitHub repository Goldziher/ai-rulez (163 stars, last pushed yesterday), licensed MIT. It adds 10 tokens to every session and 199 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-30.
Other commands, from other repositories
test
Run tests for the iOS app or specific module.
write-skill-test
RED-GREEN-REFACTOR implementation for writing-skills: Baseline testing, minimal skill writing, loophole closure, and full creation checklist.
resolve-dependabot-prs
Triage open Dependabot PRs, return a quick risk/action summary table, then enter planning mode with an ordered rebase→merge→follow-up→resume resolution plan.
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.