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/vivalalova/claude-plugins-manager/agents-mdgit clone --depth 1 https://github.com/vivalalova/claude-plugins-managerWrote 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/vivalalova/claude-plugins-manager/agents-md)<a href="https://agentmods.dev/instructions/vivalalova/claude-plugins-manager/agents-md"><img src="https://agentmods.dev/badge/instructions/vivalalova/claude-plugins-manager/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.00501 | $0.00501 |
| Opus 5 | $0.00251 | $0.00251 |
| Sonnet 5 | $0.00100 | $0.00100 |
| Haiku 4.5 | $0.00050 | $0.00050 |
Grade A, and why
claude-plugins-manager 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 4d 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
Repo 驗證補充規範
本檔補充「什麼情況下才可以回報完成」。
完成前證據（強制）
- 禁止只因單一測試通過、單一路徑 UI 正常，就回報功能完成。
- 每個使用者需求都必須先改寫成可驗證的不變量，再確認所有相關 render path / 狀態分支都成立。
- 回報完成前，必須能列出
需求 -> 驗證證據；若有任何需求只能靠推論，視為未完成。
UI / 條件渲染功能（強制）
只要需求涉及顯示 / 隱藏 / filter / section / empty state / 排序 / 分組，必須建立狀態矩陣並逐格驗證。
至少檢查：
- 預設區塊 vs 自訂區塊
- 有資料 vs 被條件清空
- 一般列表 vs 搜尋 / filter 後列表
- 可見項目存在 vs 全部被 hidden / filtered
若修的是其中一個條件分支，必須主動搜尋同元件內的平行分支是否有相同判斷或過濾邏輯，不能只修眼前那一條。
回歸測試（強制）
- 產品需求若可寫成不變量，必須補 integration / UI regression test。
- 測試名稱要直接描述產品規則，而不是描述實作細節。
- 與 list / section / hidden 相關的需求，測試必須覆蓋 section 0 與非 section 0。
回報格式（強制）
回報完成時，至少要能說清楚：
- 哪個需求
- 由哪個測試或哪個實際驗證證明
- 哪些風險仍未驗證
缺任何一項，不得使用「已完成」「已修好」「可以安裝」這類結論句。
Repo-local Skills
- Claude settings docs 同步：先讀 .claude/skills/update-settings-options/SKILL.md
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.
- 4d ago First seen · 43 lines · 501 tokens per session scan A b552f3b6702a
claude-plugins-manager AGENTS.md is an instructions file published in the GitHub repository vivalalova/claude-plugins-manager (2 stars, last pushed 14d ago), licensed MIT. It adds 501 tokens to every session, about $0.0025 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
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.
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.