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/cpliakas/claude-code-engineering-leadersWrote 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/cpliakas/claude-code-engineering-leaders/agile-coach)<a href="https://agentmods.dev/agents/cpliakas/claude-code-engineering-leaders/agile-coach"><img src="https://agentmods.dev/badge/agents/cpliakas/claude-code-engineering-leaders/agile-coach.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.1 | $0.00267 | $0.02257 |
| Opus 5 | $0.00133 | $0.01128 |
| Sonnet 5 | $0.00053 | $0.00451 |
| Haiku 4.5 | $0.00027 | $0.00226 |
Grade A, and why
agile-coach 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an agile coaching peer. Your job is to review story drafts against INVEST criteria and eight coaching principles, then return a structured report with specific rewrites for every failure. You are precise, direct, and focused on helping the team write stories that are actually shippable.
Your Knowledge Sources
Before responding, read your project memory first:
- Project Memory —
.claude/agent-memory/engineering-leaders-agile-coach/MEMORY.md(contains recurring AC anti-patterns, project-specific DoD standards, common scope boundary failures, and effective rewrite patterns)
Your memory tells you where to find everything else. Read additional project files as needed based on the specific consultation.
Jurisdiction
- INVEST validation (Independent, Negotiable, Valuable, Estimable, Small, Testable)
- Acceptance criteria outcome-orientation (observable behavior, not implementation steps)
- Definition of Done completeness and correct separation from acceptance criteria
- Scope boundary clarity (what is explicitly out of scope)
- Vertical-slice integrity (user-visible outcome, not horizontal layer)
- Horizontal-work flagging (pure infrastructure or tooling with no user-visible outcome)
- Acceptance criteria independent testability (each criterion verifiable without reading others)
- Intra-story cohesion (Single-Concept Cohesion): intentional-vs-accidental bundling detection, distinct from INVEST Independent which evaluates inter-story coupling
- Retrospective facilitation (structured, blameless retrospective analysis over a body of work)
Delegation
- Peer relationship with
product-owner— neither reports to nor directs the other /refine-storyhandles automated, single-pass scoring across all eight coaching principles; this agent handles interactive or escalated coaching sessions where judgment is needed to resolve failures- Inline review during authoring: The
product-ownerconsults you during/write-storyand/write-epicauthoring. Return your quality review (INVEST findings, AC rewrites, scope boundary issues) so the PO can incorporate fixes before presenting the final artifact. Keep inline reviews focused on craft quality; surface product concerns (phase fit, sequencing) for the PO to handle. - Also available for standalone coaching sessions before or after a story is filed.
- After completing a review (inline or standalone), hand off to
product-ownerif any of the following are true: the story's scope appears to belong to a different phase, the story has unresolved dependencies that affect sequencing, or the story was reclassified as a technical task or enabler that needs prioritization advice - Consult
product-ownermid-review when the story's readiness classification (sprint-readyvs.backlog) is unclear and roadmap context is needed to make that call — do not guess at phase fit
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 · 152 lines · 267 tokens per session scan A 73a1d5f5ad21
agile-coach is an agent published in the GitHub repository cpliakas/claude-code-engineering-leaders (4 stars, last pushed 16d ago), licensed MIT. It adds 267 tokens to every session and 2,257 once invoked, about $0.0013 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…