Borrowing it
Nothing to install: this file belongs to rjenks/pf2e-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/rjenks/pf2e-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/rjenks/pf2e-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/rjenks/pf2e-mcp/agents-md)<a href="https://agentmods.dev/instructions/rjenks/pf2e-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/rjenks/pf2e-mcp/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.01869 | $0.01869 |
| Opus 5 | $0.00934 | $0.00934 |
| Sonnet 5 | $0.00374 | $0.00374 |
| Haiku 4.5 | $0.00187 | $0.00187 |
Grade A, and why
pf2e-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 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
This project is to build an MCP for Pathfinder 2nd Edition Remastered MCP server
This project can also be used to build characters which should be stored in pathbuilder compatible JSON files in the characters/ folder.
Please rely on the guides referenced from Zenith Games Guide to the Guides and don't always trust RPGBOT. https://zenithgames.blogspot.com/2019/09/pathfinder-2nd-edition-guide-to-guides.html
Track bugs and gaps as GitHub issues, not a markdown file
Known bugs, ingestion gaps, and deferred work belong in this repo's
GitHub issues, not in a
KNOWN_ISSUES.md-style file. A markdown file like that one drifts out of
sync with reality, can't be assigned/labeled/closed independently, and
isn't searchable the way an issue tracker is — that file existed once and
was retired for exactly this reason (its ~30 entries became GitHub issues
instead). File a new issue for anything discovered during a task rather
than appending to a doc; label it bug for something producing wrong
output, enhancement for missing coverage/deferred scope, or
documentation for a caveat worth recording so it doesn't get
rediscovered as a "bug" later.
Every commit ties back to at least one GitHub issue, so the why stays attached to the code and not just the what. A diff already says what changed; the issue is what says why it was worth changing — what was broken, what gap it closed, who'd hit it. Before committing:
- If an issue already covers the change (a bug being fixed, a gap being
closed), reference it in the commit message body with
Refs #N, orFixes #N/Closes #Nwhen the commit fully resolves it — that syntax auto-closes the issue on merge to the default branch, so useRefs #Ninstead if the commit only partially addresses it or the issue should stay open for follow-up. - If no issue exists yet — a new feature, a refactor, a fix for something noticed mid-task — file one first (see above) describing the why, then reference it the same way. This is true even for small changes; a one-line issue body beats no record of the motivation at all.
- Routine maintenance with no real "why" beyond the obvious (a dependency bump, a data re-ingestion re-run, a typo fix) doesn't need an issue — use judgment, but default to filing one if there's any real decision or motivation behind the change worth preserving.
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 · +75 lines · +1,053 tokens per session 4a8908788f2b
- 7d ago First seen · 62 lines · 816 tokens per session scan A 0a3be7c7db91
pf2e-mcp AGENTS.md is an instructions file published in the GitHub repository rjenks/pf2e-mcp (2 stars, last pushed 6d ago), licensed Apache-2.0. It adds 1,869 tokens to every session, about $0.0093 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.