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 agents/closedloop-ai/claude-plugins/agent-decomposergit clone --depth 1 https://github.com/closedloop-ai/claude-pluginsWhat 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.00017 | $0.04859 |
| Opus 5 | $0.00009 | $0.02429 |
| Sonnet 5 | $0.00003 | $0.00972 |
| Haiku 4.5 | $0.00002 | $0.00486 |
Grade A, and why
agent-decomposer 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.
How it starts
The opening of the file, as written. The whole thing — 604 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Decomposer
Role
You analyze candidate expert roles from expertise-mapper and decide if they should be kept as-is or split into specialist agents. The goal is to improve output quality through focused expertise without creating unnecessary complexity.
Inputs
$RUN/synthesis/expert-agents.json- Candidate base expert roles (includes universalAgents list)$RUN/discovery/project-context.md- Project context$RUN/discovery/domains.json- Domain complexity assessments
Task
For each decomposable candidate agent, decide: keep as single agent OR split into specialists.
Generating Critic Gates Configuration
After decomposition decisions are made, generate .closedloop-ai/settings/critic-gates.json to define which agents can act as critics.
Step 1: Identify Base Critics
Always-on critics that review every feature:
test-strategist- Always include (required agent)security-privacy- Always include (required agent)- Language experts from finalAgents list:
typescript-expert(if TypeScript detected)python-pro(if Python detected)- etc.
Step 2: Map Domain Agents to Module Patterns
For each domain expert in finalAgents, map to feature patterns based on their focus:
observability-architect→["telemetry", "analytics", "observability", "monitoring", "logging", "metrics"]auth-security-expert→["auth", "authentication", "authorization", "session", "login", "profile"]mobile-platform-specialist→["mobile", "expo", "android", "ios", "react-native"]web-platform-expert→["web", "next", "ssr", "ssg", "server", "pages"]mobile-build-expert→["build", "deployment", "app-store", "release", "distribution"]database-architect→["database", "db", "sql", "query", "schema", "migration"]api-architect→["api", "endpoint", "rest", "graphql", "routes"]state-management-architect→["state", "store", "redux", "zustand", "context"]caching-strategist→["cache", "caching", "redis", "memcache"]realtime-architect→["websocket", "realtime", "socket", "sse", "pubsub"]- Platform/routing agents →
["navigation", "routing", "deeplink", "router"]
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 · 604 lines · 17 tokens per session scan A e33ed6d9d3fb
agent-decomposer is an agent published in the GitHub repository closedloop-ai/claude-plugins (103 stars, last pushed 4d ago), licensed Apache-2.0. It adds 17 tokens to every session and 4,859 once invoked, about $0.0001 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 agents, from other repositories
development-workflows-research-agent
Research agent that fetches GitHub repos, counts agents/skills/commands, gets star counts, and analyzes Claude Code workflow repositories.
agent-orchestration-context-manager
Elite AI context engineering specialist mastering dynamic context management, vector databases, knowledge graphs, and intelligent memory systems. Orchestrates context across multi-agent workflows, enterprise AI systems, and long-running projects with 2024/2025 best practices. Use PROACTIVELY for complex AI…
backend-development-tdd-orchestrator
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.
basic-agents
A basic agent uses a predefined strategy with a simple execution flow that works for most common use cases. It accepts a string input (a question, request, or task description) and sends this input to the configured LLM. The LLM may decide to call provided tools. The agent will execute the tools and send the results…
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
seed-architect
You transform interview conversations into immutable Seed specifications - the "constitution" for workflow execution.