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 review-summarygit 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/review-summary)<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/review-summary"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/review-summary/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/review-summary"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/review-summary.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.00070 | $0.00604 |
| Opus 5.5 | $0.00028 | $0.00242 |
| Sonnet 5.5 | $0.00014 | $0.00121 |
| Haiku 4.5 | $0.00007 | $0.00060 |
Grade A, and why
review-summary 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.
What it actually says
Review Summary
Role: orchestrator. This skill summarizes and persists review results — it does not review code.
You have been invoked with the /review-summary skill. Generate a compact summary of the most recent code review.
Orchestrator constraints
- Do not re-analyze code. Summarize existing review results only.
- Keep summaries under 150 words. Compact summaries replace full conversation history for future sessions (per Minimum CD session closure pattern).
- Use the template exactly. Structured output enables machine parsing.
- Be concise. The 150-word limit is a ceiling, not a target. Shorter is better. No filler phrases.
Parse Arguments
Arguments: $ARGUMENTS
--from <json-file>: Read review results from a JSON file (output of/code-review --json). If not provided, summarize from the most recent/code-reviewoutput in the conversation.
Steps
1. Gather review data
If --from is specified, read the JSON file. Otherwise, look for
the most recent code review results in the current conversation
context.
Extract: overall status, agent statuses, issue counts by severity, and top issues.
2. Generate compact summary
Write a summary under 150 words following this template:
## Review: <branch> @ <short-sha> — <date>
**Status**: <PASS|WARN|FAIL> (<N> agents, <N> issues)
**Findings**:
- <top 3-5 findings, one line each, severity prefix>
**Blocked by**: <agent names that returned fail, or "none">
**Action items**: <1-3 concrete next steps>
3. Save summary
Write the summary to .claude/review-summaries/<date>-<short-sha>.md.
Create the .claude/review-summaries/ directory if it doesn't exist.
4. Report
Display the summary to the user. Note that it will be available as context in future sessions.
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 · 74 lines · 70 tokens per session scan A 624f72bd44d5
review-summary is a skill published in the GitHub repository bdfinst/agentic-dev-team (295 stars, last pushed 4d ago), licensed MIT. It adds 70 tokens to every session and 604 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-09-03.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…