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 skills/stoa-platform/stoa/parallel-reviewnpx skills add stoa-platform/stoa --skill parallel-reviewgit clone --depth 1 https://github.com/stoa-platform/stoaWrote 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/stoa-platform/stoa/parallel-review)<a href="https://agentmods.dev/skills/stoa-platform/stoa/parallel-review"><img src="https://agentmods.dev/badge/skills/stoa-platform/stoa/parallel-review.svg" alt="Measured on agentmods" 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 | $0.00040 | $0.00926 |
| Opus 5 | $0.00020 | $0.00463 |
| Sonnet 5 | $0.00008 | $0.00185 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
parallel-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 4d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parallel Review — Review multi-angle orchestree
Executer une review parallele complete sur: $ARGUMENTS
Workflow
Step 1: Charger le contexte
Si c'est un numero de PR:
gh pr view $0
gh pr diff $0 --name-only
gh pr checks $0
Si c'est un chemin de composant:
git diff main --name-only -- $0
Step 2: Determiner les reviewers necessaires
| Fichiers modifies | Subagent a lancer |
|---|---|
*.py, *.tsx, *.ts, *.rs (code applicatif) |
security-reviewer (toujours) |
*.test.*, test_*, *.spec.* |
test-writer (evaluer couverture) |
| Tout code sans tests correspondants | test-writer (identifier les manques) |
Dockerfile, k8s/, *.yaml (k8s), nginx*, charts/ |
k8s-ops |
docs/, *.md, CLAUDE.md, memory.md |
docs-writer |
docs/*.md, blog/**, *.astro (contenu public) |
content-reviewer |
Minimum: security-reviewer est TOUJOURS lance. Maximum: 4 subagents en parallele (budget tokens).
Step 3: Deleguer aux subagents
Lancer les subagents en parallele via le Task tool:
- security-reviewer: "Analyse de securite des changements de la PR $0"
- test-writer: "Evaluer la couverture de tests pour les fichiers modifies dans la PR $0. Identifier les tests manquants."
- k8s-ops (si applicable): "Valider les changements infra/k8s de la PR $0 contre la checklist k8s-deploy.md"
- content-reviewer (si contenu public): "Audit conformite du contenu public de la PR $0 contre content-compliance.md"
Step 4: Synthetiser les resultats
Combiner les rapports des subagents en un rapport unifie:
## Review Parallele: $ARGUMENTS
### Date: [date]
### Branche: [branch]
### Fichiers modifies: [count]
---
### Securite (security-reviewer)
**Verdict**: Go / Fix / Refaire
[Resume des findings]
### Tests (test-writer)
**Verdict**: Go / Fix / Refaire
[Resume: couverture actuelle, tests manquants]
### Deployment (k8s-ops)
**Verdict**: Go / Fix / Refaire / N/A
[Resume ou "Pas de changements infra detectes"]
### Conformite Contenu (content-reviewer)
**Verdict**: Go / Fix / Refaire / N/A
[Resume: concurrents, clients, prix, reglementations, disclaimers — ou "Pas de contenu public modifie"]
---
### Verdict global: **Go** / **Fix** / **Refaire**
### Actions requises
1. [Action specifique avec fichier et ligne]
2. ...
### Actions suggerees (non-bloquantes)
1. ...
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.
- 4d ago First seen · 106 lines · 40 tokens per session scan A 331c7b120013
parallel-review is a skill published in the GitHub repository stoa-platform/stoa (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 40 tokens to every session and 926 once invoked, about $0.0002 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
lyrik
Security assessment of a codebase — minimal mode for runner validation.
librarian
Read-only retrieval over the daily-digest kept set. Slash-invoke with /librarian ; returns items verbatim with citations.
notes
Create and manage text notes in the workspace.
tdx-assets
Look up staff devices, assets, and locations in TeamDynamix (TDX). Given a list of names, emails, or partial identifiers, resolve each person and return the assets assigned to them with location, model, ownership type, and status. Read-only.
aggregator
Daily fetch from a fixed public allowlist; score against the user's interests file; cluster into themes; push the digest to the configured channel.
csv-tools
Parse and analyze CSV data.