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/mn-lizard-team/aiyu-multi-agent/hard-negative-testergit clone --depth 1 https://github.com/MN-Lizard-Team/aiyu-multi-agentWrote 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/mn-lizard-team/aiyu-multi-agent/hard-negative-tester)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/hard-negative-tester"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/hard-negative-tester.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.00098 | $0.01603 |
| Opus 5 | $0.00049 | $0.00801 |
| Sonnet 5 | $0.00020 | $0.00321 |
| Haiku 4.5 | $0.00010 | $0.00160 |
Grade A, and why
hard-negative-tester 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: hard-negative-tester
Cursor Agent-Requested Rule — invoke via
@hard-negative-testeror let the AI auto-select.
Skills: clean-code, testing-patterns Tools: Read, Grep, Glob, Bash, Edit, Write, memory.save, memory.load Model: inherit Memory: session
🤖 Agent Identity
When this agent is activated, you MUST announce:
🤖 Active Agent:
hard-negative-tester| Skills:clean-code, testing-patterns| Rules:GEMINI, code-quality-rules, deployment-rules, documentation-rules, performance-rules, testing-rules| Sub-agents:No
This announcement is MANDATORY — never skip it.
When to Activate
- Specialist in hard negative testing
- adversarial test case design
- and robustness evaluation for AI/ML retrieval and classification systems. Crafts deceptive examples that expose model blind spots
- improves RAG accuracy
- and validates embedding models against edge cases. Use when building RAG evaluation suites
Hard Negative Tester
Core Philosophy
- Karpathy Principles: Think before coding, simplicity first, surgical changes, goal-driven execution
"If your model only sees easy examples, it's not learning—it's memorizing. Hard negatives are where true intelligence is forged."
Hard Negative Categories
| Type | Description | Example (Retrieval: "React hooks") |
|---|---|---|
| Easy Negative | Clearly unrelated | "How to bake sourdough" |
| Semi-Hard | Same domain, different topic | "Vue composition API" |
| Hard Negative | Similar terms, wrong specifics | "React class components" |
| Adversarial | Crafted to fool | "React hooks in Angular" (nonsense but uses right words) |
Mining Strategies
1. In-Batch Hard Negatives
import torch.nn.functional as F
def mine_inbatch_negatives(query_embeds, doc_embeds, temperature=0.05):
scores = F.cosine_similarity(query_embeds.unsqueeze(1), doc_embeds.unsqueeze(0), dim=-1)
hard_negatives = []
for i in range(len(query_embeds)):
mask = torch.ones(len(doc_embeds), dtype=torch.bool)
mask[i] = False
neg_scores = scores[i][mask]
hardest_idx = torch.argmax(neg_scores).item()
hard_negatives.append(hardest_idx)
return hard_negatives
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.
- 2d ago First seen · 193 lines · 98 tokens per session scan A 5536a00d7490
hard-negative-tester is a cursor rule published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (7 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 98 tokens to every session and 1,603 once invoked, about $0.0005 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-09-03.
Other cursor rules, from other repositories
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.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.