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/forger-labs-hq/researchforge/researchforge-validategit clone --depth 1 https://github.com/forger-labs-hq/researchforgeWrote 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/forger-labs-hq/researchforge/researchforge-validate)<a href="https://agentmods.dev/rules/forger-labs-hq/researchforge/researchforge-validate"><img src="https://agentmods.dev/badge/rules/forger-labs-hq/researchforge/researchforge-validate.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.00000 | $0.00395 |
| Opus 5 | $0.00000 | $0.00198 |
| Sonnet 5 | $0.00000 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
researchforge-validate 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 4d 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
Validate finalists
"Validated" is a structural claim in ResearchForge: it requires the full benchmark plus the contract's configured number of repeated validation runs. A one-off result can never be called validated — the engine enforces this, and so should your language.
Validation repeats the full benchmark, so it costs real time. Tell the user how many repeats the contract configures, get their go-ahead in chat, then:
researchforge validate <run-id> --json
(The command asks for a typed confirmation; only pass --yes if the user
explicitly approved validation in this conversation.)
Afterwards, report from the JSON:
- per-attempt measurements and their spread (mean/stdev) — repeated runs exist precisely to expose variance, so show it;
- whether hard constraints held on every attempt;
- the final status: an experiment that survives becomes
validated; one that regresses stays honest too — report that as the finding it is.
Next: the researchforge-ship rule turns a validated winner into a clean branch, report, and optional draft PR.
Rules
- The Python engine is the boundary: never work around a validation error, a protected path, or an approval gate — fix the artifact or ask the user.
- Approvals belong to the user: never pass
--yesor type a confirmation unless the user explicitly approved that step in this conversation. - Ground every summary in stored data: quote only numbers returned by
--jsonoutput or files under.researchforge/— never invent metrics.
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.
- 4d ago First seen · 43 lines · 0 tokens per session scan A 7be41fe2cd49
researchforge-validate is a cursor rule published in the GitHub repository forger-labs-hq/researchforge (7 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 395 tokens. 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
pro-deck-builder
Create polished HTML slide decks and PDF-ready documents for consulting deliverables. Uses the RRBC design system with warm light mode, dark mode cover pages, Lora/Inter/Roboto Mono typography, and data visualization palette. Trigger on 'deck', 'slides', 'presentation', 'pitch deck', 'keynote', 'report', or 'PDF'.
release-notes
Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.
facebook-ads
Meta Ads (Facebook & Instagram) platform expertise. Audit campaigns, audiences, creative strategy, pixel tracking, and CAPI. Use when the user asks about Facebook Ads, Instagram Ads, Meta Ads, social media advertising, Advantage+ campaigns, or Meta pixel/CAPI setup.
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.