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 instructions/mrodgersjs-web/rigforge/agents-mdgit clone --depth 1 https://github.com/mrodgersjs-web/rigforgeWhat 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.00147 | $0.00147 |
| Opus 5 | $0.00073 | $0.00073 |
| Sonnet 5 | $0.00029 | $0.00029 |
| Haiku 4.5 | $0.00015 | $0.00015 |
Grade A, and why
rigforge AGENTS.md 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 yesterday.
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
AGENTS.md — RIGForge
Mission
Deterministic agentic engineering platform and ProofPacket engine
Hard rules
- Evidence before claims. If smoke fails, the claim is false.
- Do not add secrets, PII, prospect data, or client confidential material.
- Do not weaken public-boundary.md.
- Prefer updating smoke over writing aspirational README text.
- Builder ≠ Verifier for completion claims.
Default commands
bash scripts/smoke.sh
Load order
- Profile README (mrodgersjs-web)
- doctrine (if relevant)
- this AGENTS.md
- docs/public-boundary.md
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.
- yesterday First seen · 23 lines · 147 tokens per session scan A 4b36e951440c
rigforge AGENTS.md is an instructions file published in the GitHub repository mrodgersjs-web/rigforge (0 stars, last pushed 7d ago), licensed MIT. It adds 147 tokens to every session, about $0.0007 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-08-31.
Other instructions, from other repositories
harbor AGENTS.md
AGENTS.md instructions for harbor-framework/harbor, covering claude.md - harbor framework, contributing, project overview, quick start commands and install.
AgentEval copilot-instructions.md
Instructions for AgentEvalHQ/AgentEval, covering agenteval - ai coding agent instructions, architecture overview, environment setup, optional: secondary models for comparison and build & test commands.
AgentEval maf-updates.instructions.md
Instructions for detecting and adapting to Microsoft Agent Framework (MAF) breaking changes.
AgentEval maf-upgrade-preparation.instructions.md
Instructions for analyzing a new MAF version and producing an upgrade plan BEFORE updating the NuGet package.
AgentEval tracing.instructions.md
Guidelines for implementing trace recording and replay.
AgentEval samples.instructions.md
Guidelines for creating AgentEval samples.