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/infraspecdev/tesseract/plan-reviewnpx skills add infraspecdev/tesseract --skill plan-reviewgit clone --depth 1 https://github.com/infraspecdev/tesseractWrote 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/infraspecdev/tesseract/plan-review)<a href="https://agentmods.dev/skills/infraspecdev/tesseract/plan-review"><img src="https://agentmods.dev/badge/skills/infraspecdev/tesseract/plan-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.00045 | $0.01189 |
| Opus 5 | $0.00023 | $0.00594 |
| Sonnet 5 | $0.00009 | $0.00238 |
| Haiku 4.5 | $0.00005 | $0.00119 |
Grade A, and why
plan-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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Review
Dispatch parallel expert reviewer agents against a plan document to produce a scored analysis with prioritized recommendations and an enhanced plan.
When to Use
- User asks to review a plan, architecture doc, or execution plan
- After plan-docs skill generates a plan
- User mentions "plan review", "review my plan", "review this document"
- User invokes
/plan-review
When NOT to Use
- Code review — use code-reviewer agents instead
- Single-page design docs without stories or infrastructure — overkill
- Non-plan documents (READMEs, changelogs, runbooks) — wrong tool
Persona Catalog
| Agent | File | Weight | Focus |
|---|---|---|---|
| Cloud Architect | agents/cloud-architect-reviewer.md |
1.0 | Infrastructure, scalability, HA, ops readiness |
| Security Engineer | agents/security-engineer-reviewer.md |
1.0 | Security, threat modeling, testability |
| DX Engineer | agents/dx-engineer-reviewer.md |
1.0 | Clarity, actionability, software architecture |
| Cost/FinOps | agents/cost-finops-reviewer.md |
0.7 | Cost awareness, right-sizing, env tiering |
| Agile Coach | agents/agile-coach-reviewer.md |
0.7 | Sprint-readiness, story quality, dependencies |
Dynamic Persona Selection
digraph persona_selection {
rankdir=TB;
node [shape=box];
read [label="Read plan, extract keywords"];
has_stories [label="Plan has stories?" shape=diamond];
force_dx_ac [label="Force-include\nDX Engineer + Agile Coach"];
count_triggers [label="Count trigger keyword\nmatches per agent"];
enough [label="3+ agents selected?" shape=diamond];
add_next [label="Add next-closest\nagent by trigger count"];
announce [label="Announce selection\nto user with reasons"];
read -> has_stories;
has_stories -> force_dx_ac [label="yes"];
has_stories -> count_triggers [label="no"];
force_dx_ac -> count_triggers;
count_triggers -> enough;
enough -> announce [label="yes"];
enough -> add_next [label="no"];
add_next -> enough;
}
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 110 lines · 45 tokens per session scan A 1d28721e724a
plan-review is a skill published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 1,189 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
sred-project-organizer
Take a list of projects and their related documentation, and organize them into the SRED format for submission.
moai-workflow-project
Integrated project management system covering documentation, language initialization, template optimization, docs generation, and JIT document loading. Absorbed from moai-workflow-templates, moai-docs-generation, and moai-workflow-jit-docs.
paper-sprint-review
Scrum-inspired paper review, revision, and R&R workflow. Handles docx/tex/md/PDF in English or Chinese. Auto-detects manuscript stage, estimates sprint count, runs multi-lens review (Contribution/Rigor/Writing/Editor), generates prioritized revision backlog, exports MD/DOCX/PDF/HTML reports. Use when asked to review a…
bkit-templates
PDCA + Sprint document templates — Plan, Design, Analysis, Report for individual features plus templates/sprint/{master-plan, prd, plan, design, iterate, qa, report}.template.md for sprint-level documents (v2.1.13). Triggers: template, plan document, design template.
notion-sync
Read, create, and update Notion pages and databases. Requires Notion API integration token.
aidlc-outcomes-pack
Generate a comprehensive handover document at workflow close so the team can own, operate, and continue the system without re-running the workflow. Stage/phase/learning counts come from aidlc-runtime.ts summary; prose comes from the artefacts. Writes OUTCOMES.md but never mutates workflow state or emits audit events.