Borrowing it
Nothing to install: this file belongs to hardened-steel/ForgeMCP. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hardened-steel/ForgeMCP/main/AGENTS.mdgit clone --depth 1 https://github.com/hardened-steel/ForgeMCPWrote 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/instructions/hardened-steel/forgemcp/agents-md)<a href="https://agentmods.dev/instructions/hardened-steel/forgemcp/agents-md"><img src="https://agentmods.dev/badge/instructions/hardened-steel/forgemcp/agents-md.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.00466 | $0.00466 |
| Opus 5 | $0.00233 | $0.00233 |
| Sonnet 5 | $0.00093 | $0.00093 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
ForgeMCP 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 3d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ForgeMCP agent guide
Project
ForgeMCP is a Python MCP server providing structured and safe C++ development capabilities: workspace operations, CMake/build/test, clangd integration, and native debugging.
Read first
Before designing or changing a module, read:
README.mddocs/architecture.md- Relevant decisions in
docs/adr/ - The tests closest to the module being changed
Architecture rules
src/forgemcp/core/owns application composition, configuration, lifecycle, service registration, error conversion, and logging.- Core must not contain CMake, workspace, clangd, debugger, or process business logic.
- New capabilities belong in separate modules and are registered through
ServiceRegistry. - Domain models must be transport-neutral. Do not expose MCP, LSP, CMake, or DAP implementation types outside their adapters.
- File access must remain scoped to the configured workspace.
- Never write file contents or secrets to logs.
Development conventions
- Python 3.11+; use type annotations for public APIs.
- Prefer explicit dependencies over implicit global state.
- Add or update unit tests for behaviour changes.
- Keep MCP stdio output clean; operational logs go to stderr.
- Do not change public contracts without documenting the decision in
docs/adr/.
Validation
.\.venv\Scripts\python.exe -m pytest -q
Agents may run the following local, non-destructive workspace commands without additional confirmation:
npm run build --prefix frontend
npm test --prefix frontend
.\.venv\Scripts\python.exe -m pytest ...
.\.venv\Scripts\python.exe -m compileall ...
git diff --check
npm ci --prefix frontend may need network access when dependencies are first
installed or the lockfile changes; any Codex sandbox approval for that command
is a host-policy decision, not something this repository can disable.
Documentation ownership
Stable onboarding and rules: AGENTS.md Current system design: docs/architecture.md Rationale for irreversible decisions: docs/adr/ Work status and ordering: docs/roadmap.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.
- 3d ago Changed · +15 lines · +113 tokens per session a80c68b9825f
- 7d ago First seen · 50 lines · 353 tokens per session scan A 7e20c5117898
ForgeMCP AGENTS.md is an instructions file published in the GitHub repository hardened-steel/ForgeMCP (0 stars, last pushed 2d ago), licensed MIT. It adds 466 tokens to every session, about $0.0023 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
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.