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/bambooshadow-studio/mcp-power-packWrote 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/bambooshadow-studio/mcp-power-pack/ai-test-generation)<a href="https://agentmods.dev/rules/bambooshadow-studio/mcp-power-pack/ai-test-generation"><img src="https://agentmods.dev/badge/rules/bambooshadow-studio/mcp-power-pack/ai-test-generation.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.1 | $0.00299 | $0.00299 |
| Opus 5 | $0.00150 | $0.00150 |
| Sonnet 5 | $0.00060 | $0.00060 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
ai-test-generation 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 6d 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
Rule Name: ai-test-generation Description: Generate comprehensive tests when creating or modifying code. Use the appropriate test framework for the language. Filters:
- file: "*.py"
- file: "*.js"
- file: "*.ts"
- file: "*.rs"
- file: "*.go"
// TEST GENERATION GUIDE
Test Coverage Requirements
- Unit tests for all new functions and methods
- Integration tests for API endpoints and database operations
- Edge case tests (empty input, invalid input, boundary values)
- Error path tests (exception handling, error states)
Framework Per Language
- Python: pytest
- JavaScript/TypeScript: vitest or jest
- Rust: cargo test
- Go: go test
Test Structure
// Unit test pattern
describe('function/component name', () => {
it('should handle normal case', () => { ... })
it('should handle edge case', () => { ... })
it('should handle error case', () => { ... })
})
Naming Convention
- test_[function_name]_[scenario]
- [function] should [expected behavior] when [condition]
What to Test
- Happy path: normal inputs produce expected outputs
- Edge cases: empty/null/undefined inputs, max/min values
- Error handling: invalid inputs, network failures, auth failures
- State changes: verify side effects and state mutations
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.
- 6d ago First seen · 43 lines · 299 tokens per session scan A 3549d9376073
ai-test-generation is a cursor rule published in the GitHub repository bambooshadow-studio/mcp-power-pack (1 stars, last pushed 2mo ago), licensed MIT. It adds 299 tokens to every session, about $0.0015 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
tests
Rules for test files — keep tests lean and pattern-matched.
testing
Optional Spring Boot example-pack testing rules. Apply only when editing an adopted project or spring-boot profile output.
tell-proof-verify
Auto-run Tell Proof verification after UI-changing edits.
tell-testing
Tell testing and verification expectations.
core
The engineering contract for this repo lives in AGENTS.md (auto-loaded). Follow it. This rule only adds Cursor-specific behavior so the contract is not duplicated token-for-token on every request.
frontend
UI/component conventions. Apply when building or changing user-facing frontend code.