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 akka/ai-marketplace --skill reviewgit clone --depth 1 https://github.com/akka/ai-marketplaceWrote 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/akka/ai-marketplace/review)<a href="https://agentmods.dev/skills/akka/ai-marketplace/review"><img src="https://agentmods.dev/badge/skills/akka/ai-marketplace/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/akka/ai-marketplace/review"><img src="https://agentmods.dev/badge/skills/akka/ai-marketplace/review.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.00022 | $0.02084 |
| Opus 5 | $0.00011 | $0.01042 |
| Sonnet 5 | $0.00004 | $0.00417 |
| Haiku 4.5 | $0.00002 | $0.00208 |
Grade A, and why
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 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
You MUST consider the user input before proceeding (if not empty).
Review Modes
This review supports two modes:
- Full review (default): Reviews the entire project against Akka SDK best practices. Runs the complete checklist below. Use this when no specific feature is mentioned, or when the user explicitly asks for a project-wide review.
- Feature review: Reviews the implementation of a specific feature against its spec, plan, and constitution, in addition to the best practices checklist. Activated when the user names a feature, or when SDD artifacts (spec, plan, tasks) exist and the user doesn't explicitly ask for a general review.
Outline
Steps 1-4: SDD alignment (feature review mode only)
Skip these steps entirely in full review mode.
-
Setup: Call
akka_sdd_list_specsto find the target feature. Load the spec, plan, tasks, and checklist. -
Load context: Read the constitution using
akka_sdd_constitution. Understand what patterns and rules must be followed. -
Review implementation against spec:
- Are all functional requirements implemented?
- Are all acceptance criteria met?
- Are there deviations from the spec? If so, are they justified?
-
Review implementation against constitution:
- Apply project-specific principles and rules from the constitution
- Check that architectural decisions align with documented rationale
Step 5: Akka SDK best practices checklist (always runs)
Load the review checklist. First check if a project-level checklist exists at
.akka/review-checklist.md — if it does, use that (read the file directly).
If not, fall back to akka_sdd_get_template with template name
review-checklist to use the plugin default. Walk through every check. For
each check, report PASS, WARN (acceptable deviation with reason), or FAIL
(must fix). For WARN and FAIL items, cite the specific file(s) and line(s).
Step 6: Runtime verification (optional, either mode)
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 Changed · +3 lines 2be365a368b0
- 11d ago First seen · 175 lines · 22 tokens per session scan A b19229d23a1b
review is a skill published in the GitHub repository akka/ai-marketplace (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 22 tokens to every session and 2,084 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-31.
Other skills, from other repositories
gsd-code-review
Review source files changed during a phase for bugs, security issues, and code quality problems.
gsd-ns-review
Route to the appropriate quality / review skill based on the user's intent. gsd-code-review-fix was absorbed by gsd-code-review --fix in #2790.
gsd-pr-branch
Create a clean PR branch by filtering out .planning/ commits — ready for code review.
spec-kitty-implement-review
Orchestrate the implement-review loop for Spec Kitty work packages using any configured agent. Covers agent dispatch, state transitions, rejection cycles, arbiter escalation, and dependency-aware sequencing across all 13 supported coding agents. Triggers: "implement and review WPs", "run the implement-review loop"…
spec-kitty-mission-review
Review a fully merged Spec Kitty mission post-merge (all WPs done/approved) to verify spec→code fidelity, FR coverage, drift, risks, and security. Triggers: "review the merged mission", "post-merge mission review", "verify the completed mission", "audit the mission implementation", "mission-level acceptance review"…
spec-kitty-runtime-review
Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only…