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.
/plugin marketplace add MSApps-Mobile/claude-pluginsnpx agentmods add plugins/msapps-mobile/claude-plugins/agents-md-optimizergit clone --depth 1 https://github.com/MSApps-Mobile/claude-pluginsGrade A, and why
agents-md-optimizer 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
{
"name": "agents-md-optimizer",
"version": "1.0.1",
"description": "Audit bloated agent-instruction files (CLAUDE.md, AGENTS.md, and their variants) and rewrite them lean, or author a new one from scratch following the 200-line recipe-book principle. Detects anti-patterns like embedded API docs, negative rules, tutorials, and preemptive file preloads.",
"author": {
"name": "MSApps"
},
"repository": "https://github.com/MSApps-Mobile/claude-plugins",
"license": "MIT",
"keywords": [
"claude-md",
"agents-md",
"context-optimization",
"token-efficiency",
"agent-instructions",
"prompt-engineering",
"msapps"
],
"topics": [
"sosa-agents"
],
"sosa": {
"compliant": true,
"level": 2,
"methodology": "https://github.com/MSApps-Mobile/claude-plugins/blob/main/docs/SOSA.md"
},
"privacy_policy": "https://opsagents.agency/privacy",
"terms_of_service": "https://opsagents.agency/terms"
}
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 · 30 lines scan A f257cceec8da
agents-md-optimizer is a plugin published in the GitHub repository MSApps-Mobile/claude-plugins (9 stars, last pushed 6d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
cs2-modding
Teach your coding agent to write Cities: Skylines II code mods (Claude Code, Codex CLI): the game's architecture, the modding techniques and the game mechanics behind them, every claim verified against the decompiled game. Knowledge only, no MCP server.
memory-loop
A memory lifecycle for Claude Code's native file-based memory: a save gate against hallucinated memories, tiered expiry (short-tier memories archived — never deleted — when they lapse), a propose-then-confirm consolidation pass (merge/dedupe long-tier memory), a periodic learning-review nudge, a two-file habit frame…
cantrips
The core engineering loop for coding agents (Claude Code, Codex CLI): grill, spec, tickets, implement with TDD at agreed seams, review, commit, plus a user-gated compound step that turns session learnings into durable project memory. Basic spells a caster always has prepared.
code-to-content
Plugin marketplace listing 1 plugin: code-to-content.
code-to-content
Transform codebases into developer content. 6-phase gated workflow, 3 parallel agents, 9 content formats (blog, tutorial, Twitter, LinkedIn, README, newsletter, video script, conference talk, product launch).
legacy-analyzer
使用多個專門代理配合基於置信度的評分系統,分析 Legacy Java Spring Boot 專案並產生高品質教學文件.