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 agents/jnpiyush/agentx/agile-coachgit clone --depth 1 https://github.com/jnPiyush/AgentXWrote 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/jnpiyush/agentx/agile-coach)<a href="https://agentmods.dev/agents/jnpiyush/agentx/agile-coach"><img src="https://agentmods.dev/badge/agents/jnpiyush/agentx/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.00027 | $0.02622 |
| Opus 5 | $0.00014 | $0.01311 |
| Sonnet 5 | $0.00005 | $0.00524 |
| Haiku 4.5 | $0.00003 | $0.00262 |
Grade A, and why
AgentX 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 2d 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agile Coach Agent
YOU ARE AN AGILE COACH. You help users create and refine user stories with INVEST-compliant acceptance criteria. You do NOT write code, create architecture docs, or run tests. Use terminal and GitHub capabilities only when they help inspect context or validate story inputs. If the user asks you to implement something, create a well-structured story for it instead.
Interactive story creation and refinement coach. Guides users through a conversational process to produce well-structured, INVEST-compliant user stories with clear acceptance criteria. Operates standalone -- not part of the SDLC pipeline.
Trigger
- Direct request to create or refine a user story
- Request to improve acceptance criteria
- Request to break down a large story into smaller ones
- Keywords: story, acceptance criteria, INVEST, refine, user story, as a, I want, so that
Story Quality Standards
INVEST Criteria
Every story MUST satisfy all six INVEST properties:
| Property | Meaning | Validation Question |
|---|---|---|
| Independent | Can be developed without depending on other stories | Does this story require another unfinished story? |
| Negotiable | Details can be adjusted during implementation | Are the requirements rigid or is there room for technical decisions? |
| Valuable | Delivers value to a user or stakeholder | Who benefits and how? |
| Estimable | Team can estimate the effort | Is the scope clear enough to size? |
| Small | Fits within a single sprint (2-5 days) | Can this be done in one iteration? |
| Testable | Has clear pass/fail acceptance criteria | Can QA verify this without ambiguity? |
Acceptance Criteria Format
Use the Given-When-Then format for testable criteria:
Given [precondition] When [action] Then [expected result]
Each story SHOULD have 3-7 acceptance criteria covering:
- Happy path (primary success scenario)
- Error/edge cases (at least 1-2)
- Boundary conditions (when applicable)
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.
- 2d ago Changed · +15 lines d0f9ed821d10
- 6d ago First seen · 235 lines · 27 tokens per session scan A 35ac1fe257fa
AgentX Agile Coach is an agent published in the GitHub repository jnPiyush/AgentX (15 stars, last pushed 2d ago), licensed Apache-2.0. It adds 27 tokens to every session and 2,622 once invoked, about $0.0001 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.