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.
npx agentmods add rules/tecnomanu/agent-rules-kit-mcp/auto-testgit clone --depth 1 https://github.com/tecnomanu/agent-rules-kit-mcpWrote 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/rules/tecnomanu/agent-rules-kit-mcp/auto-test)<a href="https://agentmods.dev/rules/tecnomanu/agent-rules-kit-mcp/auto-test"><img src="https://agentmods.dev/badge/rules/tecnomanu/agent-rules-kit-mcp/auto-test.svg" alt="Measured on agentmods" 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 | $0.00212 | $0.00212 |
| Opus 5 | $0.00106 | $0.00106 |
| Sonnet 5 | $0.00042 | $0.00042 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
auto-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 3d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 37 lines · 212 tokens per session scan A 804149d8455a
auto-test is a cursor rule published in the GitHub repository tecnomanu/agent-rules-kit-mcp (3 stars, last pushed 11mo ago), with no licence file. It adds 212 tokens to every session, about $0.0011 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-31.
Other cursor rules, from other repositories
tdd
Final Verification: Always use: go test -v ./backend/api/handler/... | grep FAIL.
workflow
BDD-style workflow, UI screenshots in the PR, HTTP OpenAPI and config schema sync before lint, final checks.
agent-routing.pi-input-intercept
Codex 模型經 Pi machine dispatch 提出問題時的攔截、評估、代答或升級 protocol；觸及 spectra change / screenshot 情境時 path-scoped 載入.
mcpnuke-tests
Test conventions for mcpnuke — enforces TDD workflow.
tdd-workflow
Test-Driven Development workflow for implementing features. Activate when writing code — guides through the red-green-refactor cycle.
testing-discipline
TDD, BDD, and testing best practices — stack-agnostic.