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 skills add bdfinst/agentic-dev-team --skill claude-setup-reviewgit clone --depth 1 https://github.com/bdfinst/agentic-dev-teamWrote 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/skills/bdfinst/agentic-dev-team/claude-setup-review)<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/claude-setup-review"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/claude-setup-review/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/skills/bdfinst/agentic-dev-team/claude-setup-review"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/claude-setup-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00102 | $0.01251 |
| Opus 5.5 | $0.00041 | $0.00500 |
| Sonnet 5.5 | $0.00020 | $0.00250 |
| Haiku 4.5 | $0.00010 | $0.00125 |
Grade A, and why
claude-setup-review 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Setup Review
Role: orchestrator. This command dispatches the claude-setup-review agent
over the project's Claude Code configuration and aggregates one report. It does
not edit configuration itself — it coordinates.
Why this is a command and not a review lens
This agent reviews the harness, not the changeset. Its subject — CLAUDE.md,
.claude/, agent frontmatter, skill wiring — is almost never what a diff
touches, so as an automatic /code-review lens it was dead weight: Scope: always put it in an 18-lens panel for a two-file JavaScript change in a project
with no Claude configuration at all. Harness quality is real, but it changes on
its own schedule, so it gets its own command instead of a seat in every review.
/code-review therefore does not dispatch this agent. Run this command
after adding or restructuring CLAUDE.md, agents, or skills, or periodically as a
health check.
Related but distinct:
/agent-auditchecks structural compliance of this plugin's own agents, skills, and hooks — a mechanical conformance gate.- This command reviews your project's Claude setup for completeness and clarity, which is a judgement call.
/agent-readinessscores the whole repository against the Agent-Readiness Scorecard; this command is narrower and deeper on the configuration itself.
This command is executed under orchestrator direction. Dispatch the agent with
its model:/effort: frontmatter as declared — the harness resolves both
fields natively before dispatch, per Model/Effort Resolution in
agents/orchestrator.md (ADR 0026).
Orchestrator constraints
- Advisory only. Aggregate findings and recommendations. Do not edit
CLAUDE.md, agent files, or skill files. Hand actionable fixes to
/apply-fixesor make them yourself only on explicit instruction. - Report absence plainly. A project with no Claude configuration is a valid finding ("no CLAUDE.md — agents have no project context"), not an error. Never invent configuration that should exist without saying why.
- No double-reporting. This review owns configuration completeness and
accuracy. Defer prose quality to
doc-review, token budgets totoken-efficiency-review, and this plugin's own structural conformance to/agent-audit. When a finding belongs to one of those, drop it here. - Be concise. One aggregated report. Issue messages one sentence; recommendations map to a concrete next edit.
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 · 114 lines · 102 tokens per session scan A 6068a2f6b097
claude-setup-review is a skill published in the GitHub repository bdfinst/agentic-dev-team (295 stars, last pushed 4d ago), licensed MIT. It adds 102 tokens to every session and 1,251 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…