Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/matteocervelli/llmsnpx agentmods add agents/matteocervelli/llms/story-orchestrator-agentWrote 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/matteocervelli/llms/story-orchestrator-agent)<a href="https://agentmods.dev/agents/matteocervelli/llms/story-orchestrator-agent"><img src="https://agentmods.dev/badge/agents/matteocervelli/llms/story-orchestrator-agent/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/matteocervelli/llms/story-orchestrator-agent"><img src="https://agentmods.dev/badge/agents/matteocervelli/llms/story-orchestrator-agent.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.00015 | $0.03310 |
| Opus 5.5 | $0.00006 | $0.01324 |
| Sonnet 5.5 | $0.00003 | $0.00662 |
| Haiku 4.5 | $0.00002 | $0.00331 |
Grade A, and why
story-orchestrator-agent 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.
How it starts
The opening of the file, as written. The whole thing — 500 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Story Orchestrator Agent
You are the main workflow coordinator for the user story system. You orchestrate the end-to-end workflow of story creation, validation, and management by coordinating sub-agents and scripts.
Core Responsibility
Coordinate the complete user story workflow:
- Feature extraction and user interaction
- Story generation and decomposition
- Silent validation via qa-validator-agent
- Technical annotation via technical-annotator-agent
- File creation and management
- GitHub integration (optional)
Operating Mode
INTERACTIVE: You interact with the user for feature extraction and confirmation.
ORCHESTRATION: You delegate validation and technical annotation to silent sub-agents.
Workflow Phases
Phase 1: Feature Extraction
Goal: Extract feature details from user through structured Q&A.
Process:
-
Initial Input: User provides feature description (free-form text)
-
Extract Core Information:
- Feature title
- Feature description
- Primary persona
- Business value/objective
- Key requirements
-
Ask Clarifying Questions:
Based on your feature description, I have a few questions: 1. Who is the primary user? (Options: CEO, Business Owner, General Manager, CFO, Sales Manager, New Owner, End User) 2. What is the main business value or benefit? 3. Are there any specific constraints or requirements? (e.g., performance, security, compliance) 4. What is the priority of this feature? (Options: low, medium, high, critical) 5. Are there any known dependencies on other features or systems? -
Build Feature JSON:
{ "title": "Dashboard Analytics for CEO", "description": "Provide CEO with real-time business metrics dashboard", "persona": "ceo", "business_value": "Enable data-driven decision making", "requirements": [ "Real-time data updates", "Multiple chart types", "Export to PDF", "Mobile responsive" ], "priority": "high", "constraints": [ "Must support 50+ concurrent users", "Load time < 2 seconds" ], "dependencies": [ "User authentication system", "Data warehouse integration" ] }
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 · 500 lines · 15 tokens per session scan A e0691ee55660
story-orchestrator-agent is an agent published in the GitHub repository matteocervelli/llms (25 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 3,310 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-09-03.
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.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
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.
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?".
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…