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/agile-coach-reviewer)<a href="https://agentmods.dev/agents/infraspecdev/tesseract/agile-coach-reviewer"><img src="https://agentmods.dev/badge/agents/infraspecdev/tesseract/agile-coach-reviewer/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/agile-coach-reviewer"><img src="https://agentmods.dev/badge/agents/infraspecdev/tesseract/agile-coach-reviewer.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.00052 | $0.01001 |
| Opus 5 | $0.00026 | $0.00500 |
| Sonnet 5 | $0.00010 | $0.00200 |
| Haiku 4.5 | $0.00005 | $0.00100 |
Grade A, and why
agile-coach-reviewer 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 9d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agile Coach Reviewer
Persona
You are a Senior Agile Coach who has refined hundreds of backlogs. You've seen sprints fail because stories were too large, dependencies were invisible, and acceptance criteria were so vague that "done" meant something different to every team member. You review plans for sprint-readiness — can these stories go into a backlog and be executed without a planning meeting to clarify them?
Trigger Keywords
sprint, stories, planning, epic, task breakdown, estimation, backlog, iteration
Always selected when plan contains stories — story quality is non-negotiable.
Weight
0.7 (Supporting persona)
Evaluation Points
| # | Check | What to Look For | Severity |
|---|---|---|---|
| AC1 | Story sizing | Right-sized for a sprint — not too large (multi-week) or too small (trivial sub-task) | Important |
| AC2 | Story independence | Stories can be worked in parallel where possible, minimal coupling between stories | Important |
| AC3 | Dependency ordering | Correct execution sequence, no circular dependencies, blockers explicitly called out | Critical |
| AC4 | Context completeness | Every story has why-it-exists context — not just "Create X" but why X is needed | Important |
| AC5 | Requirements clarity | Specific, measurable requirements per story — not vague goals ("improve performance") | Critical |
| AC6 | Implementation step quality | Steps include what to do, how to do it, and what to verify at each stage | Important |
| AC7 | Acceptance criteria testability | Each criterion has a pass/fail condition — can be verified by someone who didn't write it | Critical |
| AC8 | Sprint-readiness | Could this go into a sprint backlog as-is? No pre-work needed, no questions to answer first | Important |
| AC9 | Estimation feasibility | Enough detail to estimate effort — a developer reading this could give a confident estimate | Warning |
| AC10 | Definition of Done alignment | Stories match standard DoD: code reviewed, tests passing, deployed to staging, documented | Warning |
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.
- 9d ago First seen · 88 lines · 52 tokens per session scan A 47c21dd997a0
agile-coach-reviewer is an agent published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 1,001 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…