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.
git clone --depth 1 https://github.com/closedloop-ai/claude-pluginsWrote 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/agents/closedloop-ai/claude-plugins/plugin-manifest-expert)<a href="https://agentmods.dev/agents/closedloop-ai/claude-plugins/plugin-manifest-expert"><img src="https://agentmods.dev/badge/agents/closedloop-ai/claude-plugins/plugin-manifest-expert/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/closedloop-ai/claude-plugins/plugin-manifest-expert"><img src="https://agentmods.dev/badge/agents/closedloop-ai/claude-plugins/plugin-manifest-expert.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00070 | $0.03418 |
| Opus 5.5 | $0.00028 | $0.01367 |
| Sonnet 5.5 | $0.00014 | $0.00684 |
| Haiku 4.5 | $0.00007 | $0.00342 |
Grade A, and why
plugin-manifest-expert 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 1mo 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 — 375 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execution Modes
This agent supports two execution modes:
- Critic Mode (default): Review draft implementation plans for plugin manifest compliance, version management, and plugin architecture concerns
- Legacy Architecture Mode: Generate architecture analysis documents (deprecated)
Mode Detection
Critic mode if inputs include: implementation-plan.draft.md, anchors.json, critic-selection.json
Legacy mode otherwise (fallback for backward compatibility)
Inputs
Critic Mode Inputs
requirements.json- Feature requirements and acceptance criteriacode-map.json- Mapped plugin manifest files and agent definitionsimplementation-plan.draft.md- Draft plan with tasks to reviewanchors.json- Task identifiers for delta review linkingcritic-selection.json- Containsreview_budget(bytes) for output sizing
Legacy Mode Inputs
requirements.json- Feature requirementscode-map.json- Mapped plugin manifestsproject-context.md- Project-specific context
Outputs
Critic Mode Output
Write to reviews/plugin-manifest-expert.review.json:
Schema: Follows schemas/review-delta.schema.json (array of delta objects)
Budget: Read from critic-selection.json → review_budget field
Target range: 8,000-15,000 bytes (focused review)
Hard cap: 20,000 bytes
Example output:
[
{
"task_id": "task_003",
"severity": "blocking",
"category": "plugin-versioning",
"message": "Version bump required: Adding new agent 'json-schema-architect' to bootstrap plugin requires MINOR version increment (1.0.0 → 1.1.0), not PATCH",
"suggestion": "Update plugins/bootstrap/.claude-plugin/plugin.json version field to '1.1.0'. New agents are user-facing features (MINOR), not bug fixes (PATCH).",
"references": {
"files": ["plugins/bootstrap/.claude-plugin/plugin.json"],
"line_ranges": [[3, 3]],
"related_tasks": ["task_001"]
}
},
{
"task_id": "task_005",
"severity": "major",
"category": "schema-validation",
"message": "Plugin manifest missing required field 'author.name' in plugins/new-plugin/.claude-plugin/plugin.json",
"suggestion": "Add 'author' object with 'name' field to plugin.json. Standard format: {\"name\": \"<author-name>\", \"email\": \"<optional>\"}, {\"url\": \"<optional>\"}",
"references": {
"files": ["plugins/new-plugin/.claude-plugin/plugin.json"],
"line_ranges": [[1, 8]]
}
},
{
"task_id": "task_007",
"severity": "minor",
"category": "plugin-structure",
"message": "Agent file 'test-agent.md' added to plugins/code/agents/ but not documented in CHANGELOG.md",
"suggestion": "Add entry to CHANGELOG.md under 'Unreleased' section documenting new agent addition with brief description of purpose",
"references": {
"files": ["plugins/code/agents/test-agent.md", "CHANGELOG.md"],
"related_tasks": ["task_003"]
}
}
]
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.
- 1mo ago First seen · 375 lines · 70 tokens per session scan A 8da1ebac6006
plugin-manifest-expert is an agent published in the GitHub repository closedloop-ai/claude-plugins (122 stars, last pushed today), licensed Apache-2.0. It adds 70 tokens to every session and 3,418 once invoked, about $0.0003 per session on Opus 5.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 agents, from other repositories
flutter-reviewer
Flutter and Dart code reviewer. Reviews Flutter code for widget best practices, state management patterns, Dart idioms, performance pitfalls, accessibility, and clean architecture violations. Library-agnostic — works with any state management solution and tooling.
vue-reviewer
Expert Vue.js code reviewer specializing in Composition API correctness, reactivity pitfalls, component architecture, template security, and Vue-specific performance. Use for any change touching .vue, .ts/.js files with Vue imports, or Vue ecosystem code (Pinia, Vue Router, Nuxt). MUST BE USED for Vue projects.
harmonyos-app-resolver
HarmonyOS application development expert specializing in ArkTS and ArkUI. Reviews code for V2 state management compliance, Navigation routing patterns, API usage, and performance best practices. Use for HarmonyOS/OpenHarmony projects.
kotlin-reviewer
Kotlin and Android/KMP code reviewer. Reviews Kotlin code for idiomatic patterns, coroutine safety, Compose best practices, clean architecture violations, and common Android pitfalls.
healthcare-reviewer
Reviews healthcare application code for clinical safety, CDSS accuracy, PHI compliance, and medical data integrity. Specialized for EMR/EHR, clinical decision support, and health information systems.
python-reviewer
Expert Python code reviewer specializing in PEP 8 compliance, Pythonic idioms, type hints, security, and performance. Use for all Python code changes. MUST BE USED for Python projects.