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/yash-dev007/THE-FORGEWrote 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/yash-dev007/the-forge/forge)<a href="https://agentmods.dev/rules/yash-dev007/the-forge/forge"><img src="https://agentmods.dev/badge/rules/yash-dev007/the-forge/forge/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/yash-dev007/the-forge/forge"><img src="https://agentmods.dev/badge/rules/yash-dev007/the-forge/forge.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.00000 | $0.00513 |
| Opus 5.5 | $0.00000 | $0.00205 |
| Sonnet 5.5 | $0.00000 | $0.00103 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
forge 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
THE FORGE v4 (multi-project)
When working in a repository that uses THE FORGE (presence of RESEARCH.md + EVAL_SPEC.md + EVAL.sh at the repository root), treat the project as a research loop.
Startup (each session)
- Read
FORGE_IDENTITY.md— extractForgeProjectSlugandObsidianVaultRoot. If missing →[FORGE] BLOCKED. - Read the Quintet in order:
RESEARCH.md→EVAL_SPEC.md→PROJECT_LOG.md→FORGE_SYSTEM.md→CLAUDE.md. - Validate
RESEARCH.mdcontains all eight required sections. If any blank/placeholder →[FORGE] BLOCKED. - Run the loop driver:
bash ./forge-cycle.sh --baseline-only— runs EVAL × 3, computes median, prints Status Report. - Read Obsidian patterns under
Forge/Patterns/andForge/Projects/<ForgeProjectSlug>/. - Propose exactly three hypotheses ranked by P(success). Wait for human selection.
During work
- Start every response with the
[FORGE]status line:[FORGE] Cycle N | Type: X | Hypothesis: "..." | Score: X.X → Y.Y | Δ: ±Z.Z | Decision: ... - After human implements: run
bash ./forge-cycle.sh --skip-baseline <SCORE>— script handles eval, decision, log write, Obsidian sync. - Do not modify
EVAL.shorEVAL_SPEC.mdduring hypothesis cycles (maintainer-only). - On ANOMALY output →
[FORGE] ANOMALY DETECTEDand guide revert. - Auditor every five commits; Pattern Distillation every ten cycles — counts in this repo's
PROJECT_LOG.mdonly.
If Quintet missing
Do not invent scores. Point the user to THE FORGE kit docs/ADOPT.md (path may be a sibling repo or where they installed the kit).
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 · 32 lines · 0 tokens per session scan A 5257918c7f53
forge is a cursor rule published in the GitHub repository yash-dev007/THE-FORGE (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 513 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
20-testing-generated-and-structure
Testing expectations, generated-file boundaries, and CLI structure contract.
fuzzing
Fuzzing setup and guidelines for skia-rs.
testing-and-quality
The testcomprehensive.py provides systematic testing of all 31 MCP tools.
smoke-monkey-tester
Smoke tests for core functionality and monkey/chaos tests aiming to break the system with randomized inputs. / TR: Sistemin temel fonksiyonlarını kontrol eden smoke testler ve rastgele girdilerle sistemi çökertmeyi hedefleyen monkey/chaos testleri.
testing
Testing conventions for Ion Design System using Jest and Angular Testing Library.
STAGE_S5_TEST_POINTS
A staged workflow for turning approved requirements into a complete list of test points. It checks required earlier documents and records any requirement that has no matching test point.