Borrowing it
Nothing to install: this file belongs to alexanderolvera/dfhack-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/alexanderolvera/dfhack-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/alexanderolvera/dfhack-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/alexanderolvera/dfhack-mcp/agents-md)<a href="https://agentmods.dev/instructions/alexanderolvera/dfhack-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/alexanderolvera/dfhack-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/alexanderolvera/dfhack-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/alexanderolvera/dfhack-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.01215 | $0.01215 |
| Opus 5.5 | $0.00486 | $0.00486 |
| Sonnet 5.5 | $0.00243 | $0.00243 |
| Haiku 4.5 | $0.00121 | $0.00121 |
Grade A, and why
dfhack-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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for AI coding agents working in this repo, beyond what's in CONTRIBUTING.md. CONTRIBUTING.md covers the tiered verify harness and the tool-adding checklist; this file covers code/comment hygiene — things to actively look for on every pass through this codebase, not just when asked.
Does this snippet earn its keep?
Before adding — or when passing over — a derived/curated field, function, or script, ask whether it's actually adding information, or just re-packaging something already available elsewhere in the same payload/module with a bit of prose wrapped around it. A second, hand-maintained summary of a fact is a second place for that fact to drift out of sync with the source (see the "Facts, not advice" doctrine in CONTRIBUTING.md — the same reasoning applies to internal duplication, not just advice-vs-fact).
Precedent: identify's tactics[] field (src/tools/identify/tactics.ts,
removed) derived a curated {trait, note} list — trapavoid, flier, fire,
building_destroyer, webber, ranged — from the creature dossier's own
flags[]/interactions[], which the same response already returns. It
duplicated data the caller could already see, cost a second source of truth
(its ranged derivation had its own bug — issue #66 — before the field was
cut entirely), and its removal deleted real code with no loss of information.
That's the shape to look for: a field/helper that mostly restates data sitting
one hop away in the same response.
Also watch for orphaned scripts: scripts/verify-identify.mjs (removed) had a
stale import path from before identify became a directory, and wasn't
referenced by any npm script or doc — it had already silently stopped working.
If a script/module isn't reachable from package.json, a doc, or another
module, don't assume it's still doing anything.
Comment hygiene
The target is zero comment blocks. Code should be legible enough — through naming, structure, and small functions — that it doesn't need prose alongside it to be understood. A comment is a sign the code didn't quite say what it means; prefer fixing that over documenting around it.
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 · 102 lines · 1,215 tokens per session scan A 92cb86e7c0a6
dfhack-mcp AGENTS.md is an instructions file published in the GitHub repository alexanderolvera/dfhack-mcp (2 stars, last pushed 2mo ago), licensed ISC. It adds 1,215 tokens to every session, about $0.0049 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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.