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/3akhp/prts-mcp/agents-mdgit clone --depth 1 https://github.com/3aKHP/prts-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/3akhp/prts-mcp/agents-md)<a href="https://agentmods.dev/instructions/3akhp/prts-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/3akhp/prts-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 | $0.00823 | $0.00823 |
| Opus 5 | $0.00411 | $0.00411 |
| Sonnet 5 | $0.00165 | $0.00165 |
| Haiku 4.5 | $0.00082 | $0.00082 |
Grade A, and why
prts-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 5d 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.
Codex Instructions for PRTS-MCP
This file is intentionally repo-local so a fresh Codex session starts with the known-good runtime in the current WSL2 workspace.
Branch Model
Long-lived branches after the 1.7.0 LTS release:
| Branch | Purpose | Version suffix |
|---|---|---|
main |
Latest stable release. Currently 2.7.2. |
(none) |
lts/1.7 |
1.7.x long-term maintenance. Created from the 1.7.0 release commit. | (none) |
develop |
Development integration. All non-LTS changes land here. | .dev0 (current target: 2.7.0.dev0) |
- Feature / refactor / perf / non-urgent fix / general docs / chore -> branch from
develop, PR todevelop. - 1.7.x LTS fix -> branch from
lts/1.7, PR tolts/1.7, then cherry-pick or reimplement ondevelopif applicable. - Hotfix for the latest stable line -> branch from
main, PR tomain, then forward-merge/cherry-pick todevelop. - Release -> branch from
developasrelease/vX.Y.Z, merge the release branch tomainby PR, tag onmain, then merge the same release branch back todevelopby PR.
Never push directly to main, develop, or lts/1.7. Always create a feature/fix branch and open a PR. See CLAUDE.md and docs/dev/LTS.md for the detailed iteration cycles.
Startup Reads
- Read
CLAUDE.mdanddocs/dev/STYLE.mdbefore non-trivial code changes. - Read
docs/dev/LTS.mdbefore 1.7.x compatibility, security, or release work. - Use
STATUS.mdfor current project shape and version state. - Use
ROADMAP.md/ROADMAP.zh-CN.mdwhen planning feature work.
Runtime Environment
- Host: WSL2 Linux. Keep the repository on the Linux filesystem rather than under
/mnt/<drive>for predictable permissions and filesystem performance. - Shell: use the current POSIX shell for interactive work; repository scripts target Bash when they need Bash-specific behavior.
- Python:
uvowns the project environment underpython/. Bootstrap withuv sync --directory python --lockedand run Python commands throughuv run --directory python .... Do not invokepython/.venvdirectly or rely on ambientpython. python/uv.lockis committed and must stay in sync withpyproject.toml.- Node.js: project requirement is Node >=22;
ts/package.jsoncarries the preferred Volta version. Bun >=1.3.14 is the default TS production runtime. - In WSL use normal
npm/npxcommands.
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.
- 5d ago First seen · 65 lines · 823 tokens per session scan A d1d44cd4be68
prts-mcp AGENTS.md is an instructions file published in the GitHub repository 3aKHP/prts-mcp (8 stars, last pushed 13d ago), licensed MIT. It adds 823 tokens to every session, about $0.0041 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
hayday-mcp-server CLAUDE.md
Claude Code instructions for Mohib1992/hayday-mcp-server: Purely informational read-only MCP server. See README.md for full docs.
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).
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.
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 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).
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.