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/hamzaamjad/cursor-rulesWrote 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/hamzaamjad/cursor-rules/107-sparring-techniques)<a href="https://agentmods.dev/rules/hamzaamjad/cursor-rules/107-sparring-techniques"><img src="https://agentmods.dev/badge/rules/hamzaamjad/cursor-rules/107-sparring-techniques/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/rules/hamzaamjad/cursor-rules/107-sparring-techniques"><img src="https://agentmods.dev/badge/rules/hamzaamjad/cursor-rules/107-sparring-techniques.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.00343 | $0.00343 |
| Opus 5.5 | $0.00137 | $0.00137 |
| Sonnet 5.5 | $0.00069 | $0.00069 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
107-sparring-techniques 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.
What it actually says
Sparring Techniques
Socratic Method
def socratic_challenge(claim):
questions = [
f"What evidence supports '{claim}'?",
f"When would '{claim}' fail?",
f"What's the opposite of '{claim}'?",
f"How would you test '{claim}'?"
]
return random.choice(questions)
Deliberate Flaws
# Include fixable issues for discovery
code_with_flaw = """
def get_user(id):
return db.query(f"SELECT * FROM users WHERE id={id}")
# Flaw: SQL injection vulnerability
# Discovery goal: User identifies and fixes
"""
Competing Solutions
| Problem | Solution A | Solution B | Trade-off |
|---|---|---|---|
| Caching | Redis | In-memory dict | Persistence vs Speed |
| Auth | JWT | Sessions | Stateless vs Revocable |
| Queue | RabbitMQ | Redis | Features vs Simplicity |
Evidence Demands
- "Show me the profiler output"
- "What's your actual QPS?"
- "Benchmark results?"
- "Error rate data?"
Anti-Patterns to Avoid
- Over-helping: Solving instead of guiding
- Under-challenging: Accepting first answer
- Inconsistent difficulty: Random challenge levels
- Missing validation: Not checking understanding
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 · 51 lines · 343 tokens per session scan A 788f6de2e7c9
107-sparring-techniques is a cursor rule published in the GitHub repository hamzaamjad/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It adds 343 tokens to every session, about $0.0014 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-31.
Other cursor rules, from other repositories
clean-code-reviewer
Eliminates technical debt using SOLID, DRY, YAGNI, and Addy Osmani production-grade engineering principles. / TR: SOLID, DRY, YAGNI ve Addy Osmani üretim seviyesi mühendislik ilkeleri ile kod kalitesini denetleyen yetenek.
sweep-benchmarks
Audit xrspatial modules for asv benchmark coverage gaps: missing benchmarks, backend parameterization gaps, unrepresentative inputs, broken or silently-skipped benchmarks.
code-review
BMAD BMM Agent: code-review.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.