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/patlux/pi-commandcode-provider/agents-mdgit clone --depth 1 https://github.com/patlux/pi-commandcode-providerWhat 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.00105 | $0.00105 |
| Opus 5 | $0.00053 | $0.00053 |
| Sonnet 5 | $0.00021 | $0.00021 |
| Haiku 4.5 | $0.00011 | $0.00011 |
Grade A, and why
pi-commandcode-provider 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 2d 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.
What it actually says
Agent Instructions
- Follow CONTRIBUTING.md before changing code, tests, docs, or commit messages.
- Use RELEASE.md for prerelease, npm smoke-test, stable release, tag, and GitHub follow-up work.
- Keep changes focused and reviewable; avoid unrelated refactors.
- Run the relevant checks before reporting work as done.
- Do not commit, tag, push, or publish unless explicitly asked in the current conversation.
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.
- 2d ago First seen · 8 lines · 105 tokens per session scan A d6e644700eb4
pi-commandcode-provider AGENTS.md is an instructions file published in the GitHub repository patlux/pi-commandcode-provider (131 stars, last pushed 7d ago), licensed MIT. It adds 105 tokens to every session, about $0.0005 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-30.
Other instructions, from other repositories
pi-agent-browser-native AGENTS.md
Instructions for fitchmultz/pi-agent-browser-native, covering pi-agent-browser-native, product-specific guidance, documentation placement, upstream capability baseline and command reference and tool result categories.
pi-codex-goal AGENTS.md
Instructions for fitchmultz/pi-codex-goal, covering pi-codex-goal — agent notes, local pi install policy, verify before finishing and layout.
pi-fancy-footer AGENTS.md
Instructions for mavam/pi-fancy-footer, covering pi-fancy-footer, setup, development and release engineering.
pi-subagents AGENTS.md
Instructions for tintinweb/pi-subagents, covering development rules, conversational style, code quality, documentation and commands.
pi-anthropic-auth AGENTS.md
Instructions for gotgenes/pi-anthropic-auth, covering agents guide: pi-anthropic-auth, project, primary goal, current status and principles.
supi CLAUDE.md
Instructions for mrclrchtr/supi, covering claude.md, development status, pi docs-first rule, documentation expectations and package layout convention.