agentmods.dev

story-planner

story-planner is an agent for Claude Code from nguyenthienthanh/aura-frog. It costs 46 tokens per session (1,088 once invoked), scanned A, original, MIT.

A planning agent that breaks a software story into small tasks and prepares an acceptance-test outline. TDD, or test-driven development, means writing a failing test before the code that makes it pass.

In plain words
What is it for?
Use it to expand a story into one to six tasks, create or revise story plans, and prepare acceptance tests before implementation.
Why use it?
It turns a broad piece of work into steps that one coding agent can complete and gives the work clear checks for completion.

Agent for Claude Code

Written for Claude Code: effort in frontmatter.

Part of the aura-frog plugin — 43 skills, 24 commands, 15 agents, 10 hooks, 6 MCP servers shipped together

not rated 25repo changed 3d ago A scan 46 tokens original MIT

Good fit Use it to expand a story into one to six tasks, create or revise story plans, and prepare acceptance tests before implementation.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/nguyenthienthanh/aura-frog/story-planner
View source ↗ nguyenthienthanh/aura-frog ethannguyenlabs.xyz
Install

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.

Clone the repo
git clone --depth 1 https://github.com/nguyenthienthanh/aura-frog

Made for: Claude Code.

Or install aura-frog, the plugin that ships this one along with the rest of its 43 skills, 24 commands, 15 agents, 10 hooks, 6 MCP servers.

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-planner

README.md
[![agentmods](https://agentmods.dev/badge/agents/nguyenthienthanh/aura-frog/story-planner/github.svg)](https://agentmods.dev/agents/nguyenthienthanh/aura-frog/story-planner)
Your own site
<a href="https://agentmods.dev/agents/nguyenthienthanh/aura-frog/story-planner"><img src="https://agentmods.dev/badge/agents/nguyenthienthanh/aura-frog/story-planner/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-planner

Your own site · 80×15
<a href="https://agentmods.dev/agents/nguyenthienthanh/aura-frog/story-planner"><img src="https://agentmods.dev/badge/agents/nguyenthienthanh/aura-frog/story-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,088 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.00046 $0.01088
Opus 5.5 $0.00018 $0.00435
Sonnet 5.5 $0.00009 $0.00218
Haiku 4.5 $0.00005 $0.00109

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

Security

Grade A, and why

story-planner 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 3d 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.

aura-frog/agents/story-planner.md · 83 lines

How it starts

The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent: Story Planner

STATUS — v3.7.0-alpha.1 SKELETON. Pairs with existing TDD Phase 1; full integration with run-orchestrator arrives in Milestone B.

Purpose

Owns Tier 3 (Story) → Tier 4 (Task) decomposition per spec §8.4.

A Story is one TDD-bounded unit (RED → GREEN → REFACTOR). Tasks are atoms a single agent invocation can complete. Story-planner sits at the boundary between planning and execution — it produces both the design AND the acceptance test skeleton.

When invoked

  • /aura-frog:plan-expand STORY-NNNN (T3 → T4 decomposition)
  • TDD Phase 1 entry of an active run-orchestrator workflow (auto-paired)
  • replanner triggers story-level rewrite (Milestone B+)

Constraints

  • READ-ONLY on production code

  • Writes only to (use the story's RESOLVED folder — see below):

    • <story-folder>/story.md (revisions)
    • <story-folder>/acceptance.md (test plan)
    • <story-folder>/tasks/TASK-NNNNN_<slug>/task.md (new files, v3.7.3+ folder-per-task)

    The story folder lives wherever its parent feature lives — top-level (features/<id>/stories/<story-id>/) OR under a subfeature (features/<parent>/subfeatures/<id>/stories/<story-id>/, v3.7.3+). The child_path: line printed by expand-node.sh resolves this for you — copy it verbatim. Never assume features/<feat>/stories/... is the only valid prefix.

  • MAY stub __tests__/<story-id>/*.test.cjs files with it.skip() placeholders so acceptance.md has real test_ref paths

  • Does NOT execute tests or write production code — that's the assigned agent's job in Phase 2/3

Output discipline

  • 1-6 Tasks per Story (more = signal that Story is too big)
  • Each Task:
    • Single agent (agent: tdd-engineer | architect | frontend | mobile | ...)
    • depends_on forms DAG (no cycles)
    • artifacts: [{path, functions}] for L1/L2 conflict detection
    • context_budget ≤ 2000 tokens (spec §6.6)
  • Total Story body + Task bodies ≤ 5,000 + 6×2,000 = 17,000 tokens (well under spec §6.5 cap)

Read the full file on GitHub · 83 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. 3d ago Changed e3b126d42866
  2. 1mo ago Changed 8255038bb3ec
  3. 1mo ago First seen · 83 lines · 46 tokens per session scan A 524b9ccac7a1

Subscribe to this mod's changes

story-planner is an agent published in the GitHub repository nguyenthienthanh/aura-frog (25 stars, last pushed 4d ago), licensed MIT. It adds 46 tokens to every session and 1,088 once invoked, about $0.0002 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-08-30.

Claude CodePlanningTDDTestingai-assisted-developmentai-for-developerscode-qualitycontext-engineeringdeveloper-productivity
Related

Other agents, from other repositories

gsd-debug-session-manager

Manages multi-cycle /gsd:debug checkpoint and continuation loop in isolated context. Spawns gsd-debugger agents, handles checkpoints via AskUserQuestion, dispatches specialist skills, applies fixes. Returns compact summary to main context. Spawned by /gsd:debug command.

open-gsd/gsd-core · 63 tokens

gsd-nyquist-auditor

Fills Nyquist validation gaps by generating tests and verifying coverage for phase requirements.

open-gsd/gsd-core · 24 tokens

senior-dev

Senior developer for test-first implementation. Use for implementing features or bugfixes through strict red-green-refactor TDD. Follows the test-driven-development skill.

intent-driven-dev/intent-driven-template · 32 tokens

evolve-tdd-engineer

Test-first agent for the Evolve Loop. Writes failing tests that encode acceptance criteria BEFORE Builder writes any production code. RED phase is the proof of understanding. Runs on Opus (tier-1) for anti-cooperative-bias separation from Builder's Sonnet (tier-2).

mickeyyaya/evolve-loop · 64 tokens

test-engineer

Expert in test automation, quality assurance, and test-driven development.

frankbria/codeframe · 16 tokens

evolve-spec-verifier

Spec verifier agent for the Evolve Loop. Validates and verifies acceptance criteria and specifications prior to TDD and build phases.

mickeyyaya/evolve-loop · 31 tokens