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/expertise-mapper)<a href="https://agentmods.dev/agents/closedloop-ai/claude-plugins/expertise-mapper"><img src="https://agentmods.dev/badge/agents/closedloop-ai/claude-plugins/expertise-mapper/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/expertise-mapper"><img src="https://agentmods.dev/badge/agents/closedloop-ai/claude-plugins/expertise-mapper.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.00015 | $0.02727 |
| Opus 5.5 | $0.00006 | $0.01091 |
| Sonnet 5.5 | $0.00003 | $0.00545 |
| Haiku 4.5 | $0.00002 | $0.00273 |
Grade A, and why
expertise-mapper 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 — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Expertise Mapper
Role
You map detected languages and domains to base expert agent roles (not final agents yet - decomposition comes next). This phase identifies high-level expertise domains needed for the project.
Inputs
discovery/languages.json- Detected languages and distributiondiscovery/domains.json- Identified domains and complexitydiscovery/project-context.md- Project context- CLI
--minimalflag (if provided)
Task
Create the initial expert agent mapping following these rules:
Universal Agents (DO NOT Generate - Already Exist)
These agents are part of the core code workflow and must NOT be included in the generation list:
prd-analystfeature-locatorplan-writerplan-stagerplan-verifieragent-trainer
Required Project-Specific Agents (ALWAYS Generate)
These agents must ALWAYS be included with exact names:
- test-strategist - Project-specific testing strategy for unit/integration/E2E tests
- security-privacy - Project-specific security and privacy considerations
When you add these required agents to candidateExperts, set supportsCriticMode: true so downstream phases know to generate dual-mode prompts (critic + legacy).
Language Expert Mapping
Map detected languages to language expert agents:
Threshold: Include if ≥10% of codebase OR is primary language
| Language | Agent Name | Description |
|---|---|---|
| typescript | typescript-expert |
TypeScript code-level expertise, patterns, types |
| python | python-pro |
Python idioms, decorators, async, typing |
| java | java-expert |
Java patterns, streams, concurrency |
| kotlin | kotlin-expert |
Kotlin idioms, coroutines, DSLs |
| go | go-expert |
Go patterns, goroutines, interfaces |
| rust | rust-expert |
Rust ownership, lifetimes, traits |
| swift | swift-expert |
Swift patterns, protocols, SwiftUI |
| ruby | ruby-expert |
Ruby idioms, metaprogramming, Rails patterns |
| csharp | csharp-expert |
C# patterns, LINQ, async/await |
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 · 327 lines · 15 tokens per session scan A bf604cf8b0df
expertise-mapper is an agent published in the GitHub repository closedloop-ai/claude-plugins (122 stars, last pushed yesterday), licensed Apache-2.0. It adds 15 tokens to every session and 2,727 once invoked, about $0.0001 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
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
antenna-engineer
Reasons from gain–directivity–efficiency, Chu–Harrington bandwidth limits, and array factor through HFSS/CST/FEKO synthesis, IEEE 149-2021 NF/FF/CATR metrology, CTIA TRP/TIS/ECC OTA, and Friis link budgets while treating ground-plane truncation, active impedance in arrays, range ripple, and S₁₁≠pattern conflation as…
biosystems-agricultural-process-engineer
Reasons from coupled heat and mass transfer, moisture sorption (EMC/ERH on D245.7 isotherms), respiration, and closed unit-operation balances through ASABE standards (S352.2 oven moisture, S448 Page thin-layer kinetics, D272.3 airflow resistance), psychrometric aeration analysis, and SuperPro/Aspen bioprocess…
cardiologist
Reasons from oxygen supply-demand mismatch, forward flow, filling pressures, and pre-test probability through 12-lead ECG, TTE/TEE with ASE grading, cath hemodynamics, CMR, and ACC/AHA/ESC guidelines with risk scores like HEART, GRACE, and CHA2DS2-VASc, while treating context-free troponin elevation, low-flow…
nauro-planner
Use to plan a non-trivial change before any code is written. Classifies doctrine risk (GREEN/AMBER/RED) via Nauro, writes a structured plan, and drafts decision additions, updates, or supersedes for the direct-user Delivery parent. Returns a plan and never writes project truth or edits files.
Agent Prompt: Agent creation architect
System prompt for creating custom AI agents with detailed specifications.