Borrowing it
Nothing to install: this file belongs to u9401066/nsforge-mcp. 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/u9401066/nsforge-mcp/master/AGENTS.mdgit clone --depth 1 https://github.com/u9401066/nsforge-mcpWrote 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/u9401066/nsforge-mcp/agents-md)<a href="https://agentmods.dev/instructions/u9401066/nsforge-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/u9401066/nsforge-mcp/agents-md/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/instructions/u9401066/nsforge-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/u9401066/nsforge-mcp/agents-md.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.00990 | $0.00990 |
| Opus 5.5 | $0.00396 | $0.00396 |
| Sonnet 5.5 | $0.00198 | $0.00198 |
| Haiku 4.5 | $0.00099 | $0.00099 |
Grade A, and why
nsforge-mcp 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 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NSForge Agent Harness
Workspace instructions for autonomous agents (Copilot, Cline, Codex, OpenHands, Hermes, …) working in the Neurosymbolic Forge (NSForge) repository.
Goal
Help build and operate NSForge — an MCP server that turns concepts into
verifiable, traceable entities (symbols → derivations → algorithms). The AI
orchestrates; deterministic tools reify. See
docs/reification-ladder-direction.md for the north star.
North Star
Every symbol / equation / value / line of code in a final result must have a tool call as its "birth certificate" (provenance). The AI must not hand-derive any of them.
Success = the amount the AI computes by hand approaches zero.
Working Style
- Use Traditional Chinese unless the user asks otherwise.
- Prefer exact file paths, command output summaries, and verification results.
- Offload mechanical/deterministic steps (symbolic calculation, simplification, code generation) to tools — do not hand-derive formulas.
- When changing behavior, add a focused regression test under
tests/.
Ground Truth: one command
Before and after changes, verify against the green baseline:
python scripts/check.py # all gates
python scripts/check.py --json # machine-readable summary (for agents)
python scripts/check.py --gates lint,type,test # subset
Gates: 14 total — lint, format, type, security, import, manifest, mcp, test,
bench, generic, provenance, package, harness, diff. Exit code 0 = green.
(bench = derivation-correctness of benchmarks/*.json through the L3 orchestrator;
generic = arbitrary unseen compositions derive correctly, proving NSForge is a
derivation calculus, not a hand-built formula library; provenance = every
benchmark derivation carries a complete tool-provenance ledger, no hand-derived leaks;
mcp = MCP 2.1.1 discovery, schemas, metadata, payloads, resources, prompts, and
legacy-client compatibility stay green;
security = executable source has no high-severity Bandit finding;
package = sdist/wheel build, isolated install, packaged assets, and installed MCP smoke stay green;
harness = the harness self-checks its own invariants — package version parity,
self-describing tools, and gate/doc parity — so agents can trust the signal.)
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 Changed · +10 lines · +154 tokens per session fa29bed0bd07
- 1mo ago First seen · 77 lines · 836 tokens per session scan A 983d9dc62f09
nsforge-mcp AGENTS.md is an instructions file published in the GitHub repository u9401066/nsforge-mcp (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 990 tokens to every session, about $0.0040 per session on Opus 5.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
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.