story-orchestrator-agent

story-orchestrator-agent is an agent for Claude Code from matteocervelli/llms. It costs 15 tokens per session (3,310 once invoked), scanned A, original, MIT.

A workflow coordinator for creating and managing user stories, including gathering requirements, splitting work, validating stories, and adding technical notes.

In plain words
What is it for?
It helps collect feature details, create stories, run INVEST checks, add technical annotations, manage files, and optionally connect the workflow to GitHub.
Why use it?
It brings several story-writing and review tasks into one process, so teams can move from an idea to organized, checked work items.

Agent for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 scripts/validate_story_invest.py --story-id US-0001 --save.

Good fit It helps collect feature details, create stories, run INVEST checks, add technical annotations, manage files, and optionally connect the workflow to GitHub.

Compare 6 agents from other repositories ↓
Install

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.

Clone the repo
git clone --depth 1 https://github.com/matteocervelli/llms
agentmods
npx agentmods add agents/matteocervelli/llms/story-orchestrator-agent

Made for: Claude Code.

Wrote 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.

agentmods badge for story-orchestrator-agent

README.md
[![agentmods](https://agentmods.dev/badge/agents/matteocervelli/llms/story-orchestrator-agent/github.svg)](https://agentmods.dev/agents/matteocervelli/llms/story-orchestrator-agent)
Your own site
<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.

agentmods 80×15 button for story-orchestrator-agent

Your own site · 80×15
<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>
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,310 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 1mo ago against content hash e0691ee55660, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

.archive/user-story-system/.claude/agents/story-orchestrator-agent.md · 500 lines

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:

  1. Feature extraction and user interaction
  2. Story generation and decomposition
  3. Silent validation via qa-validator-agent
  4. Technical annotation via technical-annotator-agent
  5. File creation and management
  6. 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:

  1. Initial Input: User provides feature description (free-form text)

  2. Extract Core Information:

    • Feature title
    • Feature description
    • Primary persona
    • Business value/objective
    • Key requirements
  3. 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?
    
  4. 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"
      ]
    }
    

Read the full file on GitHub · 500 lines

Changes

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.

  1. 1mo ago First seen · 500 lines · 15 tokens per session scan A e0691ee55660

Subscribe to this mod's changes

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.

Related

Other agents, from other repositories