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/agents/infraspecdev/tesseract/scope-discipline-of-plan)<a href="https://agentmods.dev/agents/infraspecdev/tesseract/scope-discipline-of-plan"><img src="https://agentmods.dev/badge/agents/infraspecdev/tesseract/scope-discipline-of-plan/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/agents/infraspecdev/tesseract/scope-discipline-of-plan"><img src="https://agentmods.dev/badge/agents/infraspecdev/tesseract/scope-discipline-of-plan.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.00069 | $0.00483 |
| Opus 5 | $0.00034 | $0.00242 |
| Sonnet 5 | $0.00014 | $0.00097 |
| Haiku 4.5 | $0.00007 | $0.00048 |
Grade A, and why
scope-discipline-of-plan 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 10d 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
Scope Discipline of Plan (PM3)
Description
Grade ONE PM dimension: is the proposed plan disciplined (MVP-shaped) or overloaded? Identify what could be cut without losing core value. This is a PLAN-level scope check — distinct from the PRD-Review dim 2 prompt that grades a PRD's Non-Goals section structurally. Return a single-check JSON block — no prose.
Inputs
doc_path— absolute path to the plan, research findings, RFC, or proposal under review
Check
| ID | Eval point | Severity | Pass criterion |
|---|---|---|---|
| PM3 | Scope discipline | Important | The plan distinguishes "must have to deliver the stated value" from "could have, deferred", with a defensible MVP cut. Kitchen-sink plans (everything is must-have) fail. Plans without any scope decisions documented fail. A B grade is allowed when the cut is mostly there but one or two items appear scope-creepy. |
Grade A (fully met) / B (minor gap) / C (partial) / D (barely) / F (absent).
Output shape (JSON only)
{
"id": "PM3",
"name": "Scope discipline (plan)",
"persona": "product-manager",
"grade": "A|B|C|D|F",
"severity": "Important",
"evidence_quote": "<verbatim line from the doc, or empty string if absent>",
"gap": "<one sentence, or null if grade A>",
"suggestion": "<one sentence, or null if grade A>"
}
evidence_quote MUST be a verbatim substring of the doc; do not paraphrase.
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.
- 10d ago First seen · 47 lines · 69 tokens per session scan A fe322accf278
scope-discipline-of-plan is an agent published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 2mo ago), licensed MIT. It adds 69 tokens to every session and 483 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-31.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…