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.
git 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/commands/infraspecdev/tesseract/plan-review)<a href="https://agentmods.dev/commands/infraspecdev/tesseract/plan-review"><img src="https://agentmods.dev/badge/commands/infraspecdev/tesseract/plan-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/commands/infraspecdev/tesseract/plan-review"><img src="https://agentmods.dev/badge/commands/infraspecdev/tesseract/plan-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.00028 | $0.00408 |
| Opus 5.5 | $0.00011 | $0.00163 |
| Sonnet 5.5 | $0.00006 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
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 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
/plan-review
Run a multi-persona plan review. This command dispatches 3-5 expert reviewer agents in parallel to evaluate a plan document, then produces a scored analysis and enhanced plan.
Usage
/plan-review [path-to-plan]
If no path is provided, auto-detect the most recently generated plan document in the working directory.
Process
- Locate the plan — use the provided path or auto-detect recent plan files (
*plan*.html,*plan*.md) - Read the plan — load the full document content
- Invoke the plan-review skill — the skill handles persona selection, parallel dispatch, scoring, and output generation
- Write output — results go to
review/<YYYY-MM-DD>-<topic-slug>/analysis.mdandplan.md
Reviewers
| Reviewer | Focus | Weight |
|---|---|---|
| Cloud Architect | Infrastructure, scalability, HA, operational readiness | 1.0 |
| Security Engineer | Security, threat modeling, testability, validation | 1.0 |
| DX Engineer | Plan clarity, actionability, software architecture | 1.0 |
| Cost/FinOps | Cost awareness, right-sizing, environment tiering | 0.7 |
| Agile Coach | Sprint-readiness, story quality, dependencies | 0.7 |
Not all reviewers run every time — the skill dynamically selects 3-5 based on plan content.
Output
review/<date>-<slug>/analysis.md— scored evaluation with per-persona grades, consolidated recommendations (P0/P1/P2)review/<date>-<slug>/plan.md— enhanced plan with review feedback applied
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 · 42 lines · 28 tokens per session scan A f3769985b908
plan-review is a command published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 408 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.