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-shipgit 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-ship)<a href="https://agentmods.dev/rules/forger-labs-hq/researchforge/researchforge-ship"><img src="https://agentmods.dev/badge/rules/forger-labs-hq/researchforge/researchforge-ship.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.00769 |
| Opus 5 | $0.00000 | $0.00385 |
| Sonnet 5 | $0.00000 | $0.00154 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
researchforge-ship 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 5d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship a validated result
Three steps, each more outward-facing than the last. Every one is gated by the engine (contract flags + typed confirmations) and each gate exists for the user to open, not you.
1. Local branch (never pushed)
researchforge ship branch --json
Requires shipping.allow_branch_creation in the approved contract and a
typed confirmation — ask the user to run it, or use --yes only with their
explicit go-ahead in this conversation. The engine re-runs the full
benchmark once (pre-ship confirmation) and refuses to ship on failure,
constraint violation, or unconfirmed improvement. The result is one clean
commit on the frozen baseline, as a local branch only — the user's
checkout and remotes are untouched. Report the branch name, commit, and
pre-ship metric from the JSON.
2. Engineering report
researchforge report build --json
Writes .researchforge/reports/engineering-report.md — the full evidence
chain (objective → baseline → experiments → rejected approaches →
validation → recommendation → exact reproduction steps), built from recorded
data only. Offer to walk the user through it.
3. Draft PR (opt-in, pushes to the remote)
researchforge ship pr --json
This pushes one branch to the user's remote and opens a draft PR via
gh. It is double opt-in: shipping.allow_draft_pr must be true in the
approved contract AND a typed push confirmation is required. Confirm with
the user in chat before this step every time; never use --yes here unless
they just told you to push. If the contract flag is off, tell the user how
to enable it (edit researchforge.yaml, re-approve the contract) — do not
look for another way to push.
Open-source / third-party repositories — ask first. Before shipping a PR, ask the user how they relate to the repository:
- They have push access (their own repo, or a repo they maintain):
ship prpushes a feature branch to it and opens the draft PR there. - They do not have push access (an open-source repo they cloned): the
engine detects this, offers to fork into their GitHub account (typed
forkconfirmation — the user must type it), pushes the branch to the fork, and opens a cross-repo draft PR against the upstream. Never fork without that typed consent, and confirm which GitHub accountghis authenticated as (gh api user -q .login) so the fork lands where the user expects.
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.
- 5d ago First seen · 77 lines · 0 tokens per session scan A b8feb8032f82
researchforge-ship is a cursor rule published in the GitHub repository forger-labs-hq/researchforge (7 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 769 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.