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 permit0-ai/permit0 --skill reviewing-plan-docsgit clone --depth 1 https://github.com/permit0-ai/permit0Wrote 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/permit0-ai/permit0/reviewing-plan-docs)<a href="https://agentmods.dev/skills/permit0-ai/permit0/reviewing-plan-docs"><img src="https://agentmods.dev/badge/skills/permit0-ai/permit0/reviewing-plan-docs.svg" alt="Measured on agentmods" 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.00056 | $0.01584 |
| Opus 5 | $0.00028 | $0.00792 |
| Sonnet 5 | $0.00011 | $0.00317 |
| Haiku 4.5 | $0.00006 | $0.00158 |
Grade A, and why
reviewing-plan-docs 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 8d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reviewing Plan Docs for permit0
When to Use
Use this skill when the user asks you to review, audit, critique, or validate
planning documents under docs/plans/<feature>/. The output is a set of
review docs written to docs/plan-reviews/<feature>/.
Workflow
Phase 1: Read the Plan
Read every file in docs/plans/<feature>/ in numbered order. For each doc,
note:
- What it claims (the design decisions, schemas, code changes).
- What assumptions it makes.
- What it explicitly defers or omits.
Phase 2: Codebase Walkthrough
Do a thorough read of the actual source code that the plan references. This is not optional -- you must verify claims against real code.
For integration plans, always read:
- The reference implementation the plan says it is based on. For example,
if the plan says "replicate the Claude Code integration," read
crates/permit0-cli/src/cmd/hook.rsend to end. - The crate(s) the plan says it will modify. Read every file in those crates, not just the ones the plan mentions.
- The crates the plan says are NOT modified. Spot-check at least the public API surface to verify the plan's claim that no changes are needed.
- Packs and risk rules if the feature touches normalization or scoring
(read
packs/permit0/email/as the reference pack). - The daemon/serve code if the feature involves
--remotemode (crates/permit0-cli/src/cmd/serve.rs). - Tests -- read existing test files to understand current coverage and what the plan's new tests need to complement.
Phase 3: Write the Review
Write review docs to docs/plan-reviews/<feature>/. One review file per
plan doc, plus a summary.
Output Structure
docs/plan-reviews/<feature>/
00-summary.md # Overall verdict and key findings
01-review-overview.md # Review of 00-overview.md
02-review-protocol.md # Review of 01-protocol.md
03-review-implementation.md # Review of 02-implementation.md
04-review-configuration.md # Review of 03-configuration.md
05-review-testing.md # Review of 04-testing.md
06-review-limitations.md # Review of 05-limitations.md
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.
- 8d ago First seen · 201 lines · 56 tokens per session scan A f32be6b17f63
reviewing-plan-docs is a skill published in the GitHub repository permit0-ai/permit0 (185 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,584 once invoked, about $0.0003 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-30.
Other skills, from other repositories
interpret-results
Interprets AIR Blackbox scan results and maps findings to specific EU AI Act articles, recitals, and remediation steps. Use when the user has scan output and wants to understand what to fix, why it matters, or how to prioritize.
compliance-scan
Scans a Python AI project for EU AI Act compliance gaps using AIR Blackbox. Use when the user asks to check compliance, scan their code, audit their AI project, or mentions EU AI Act, Articles 9-15, or compliance checking.
diff-evidence-agent
Create evidence explaining the actual implementation diff and its relationship to the predicted impact, closing the loop between pre-change prediction and post-change reality.
expert-code-review
Expert review guidelines for auditing repositories, pull requests, and system designs. Use when performing code review to find functional gaps, security risks, correctness bugs, maintainability problems, missing tests, and architectural weaknesses without making direct code changes.
governance
Validates actions, generates receipts, enables rollback.
governance
Validates actions, generates receipts, enables rollback.