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/bug-ops/mcpls/changeloggit clone --depth 1 https://github.com/bug-ops/mcplsWhat 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.00158 | $0.00158 |
| Opus 5 | $0.00079 | $0.00079 |
| Sonnet 5 | $0.00032 | $0.00032 |
| Haiku 4.5 | $0.00016 | $0.00016 |
Grade A, and why
mcpls changelog.instructions.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
Changelog format
Breaking changes to public APIs must appear under ### Changed with an explicit
"Breaking change:" prefix. A ### Fixed entry alone is not sufficient — downstream
users scanning the changelog for breakage will miss it.
Additions of #[non_exhaustive] to existing public enums or structs are breaking
changes for crates that match exhaustively. Document the required migration (add a
wildcard arm, update struct initialisation) in the entry.
Every entry must reference the PR or issue number: (#NNN).
New entries go under ## [Unreleased]. Do not add entries directly under a versioned
section — version assignment happens in the release PR.
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 · 19 lines · 158 tokens per session scan A 8d4c171724b6
mcpls changelog.instructions.md is an instructions file published in the GitHub repository bug-ops/mcpls (66 stars, last pushed 4d ago), licensed Apache-2.0. It adds 158 tokens to every session, about $0.0008 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
octocode AGENTS.md
AGENTS.md instructions for bgauryy/octocode, covering agents.md — octocode monorepo, dogfood, architecture, packages and tools.
octocode CLAUDE.md
Claude Code instructions for bgauryy/octocode: Read AGENTS.md. Discover repository skills under .agents/skills and activate only those matching the task.
leantoken AGENTS.md
Instructions for morluto/leantoken, covering repository guidance, architecture, development, change-specific validation and contributions.
rangeLink CLAUDE.md
Instructions for couimet/rangeLink: Project-specific instructions for Claude Code RangeLink - Code location link generator for VSCode/Cursor 2.0 - XML-structured format.
reposkein AGENTS.md
Instructions for reposkein/reposkein, covering reposkein knowledge base, hard invariants (ci-enforced — never break), structure, where to look and conventions (this repo only).
ScalaSemantic AGENTS.md
Instructions for MercurieVV/ScalaSemantic, covering agents.md instructions and quick start.