agentmods.dev

epic-writer

epic-writer is an agent for Claude Code from ihudak/ihudak-claude-plugins. It costs 110 tokens per session (2,776 once invoked), scanned A, original, MIT.

A file writer for creating child Epic definitions from structured project information. An Epic is a large piece of work that groups related tasks or user stories.

In plain words
What is it for?
Creating or refining one Epic-definition file per Epic, using Jira information, code-scan results, scope decisions, and existing Epics.
Why use it?
It turns prepared project findings and requirements into consistent Epic files while reducing duplicate work. It leaves version-control commits to the user.

Agent for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the dev-workflows plugin — 2 skills, 28 commands, 38 agents, 3 hooks shipped together

not rated 2repo changed 2d ago A scan 110 tokens original MIT

Good fit Creating or refining one Epic-definition file per Epic, using Jira information, code-scan results, scope decisions, and existing Epics.

Compare 6 agents from other repositories ↓
View source ↗ ihudak/ihudak-claude-plugins
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add ihudak/ihudak-claude-plugins
Claude Code
/plugin install dev-workflows

Made for: Claude Code.

Or install dev-workflows, the plugin that ships this one along with the rest of its 2 skills, 28 commands, 38 agents, 3 hooks.

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 epic-writer

README.md
[![agentmods](https://agentmods.dev/badge/agents/ihudak/ihudak-claude-plugins/epic-writer.svg)](https://agentmods.dev/agents/ihudak/ihudak-claude-plugins/epic-writer)
Your own site
<a href="https://agentmods.dev/agents/ihudak/ihudak-claude-plugins/epic-writer"><img src="https://agentmods.dev/badge/agents/ihudak/ihudak-claude-plugins/epic-writer.svg" alt="Measured on agentmods" height="20"></a>
Per session 110 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,776 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.00110 $0.02776
Opus 5 $0.00055 $0.01388
Sonnet 5 $0.00022 $0.00555
Haiku 4.5 $0.00011 $0.00278

Measured 2d ago against content hash 0ee74e504a77, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

epic-writer 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.

plugins/dev-workflows/agents/epic-writer.md · 171 lines

How it starts

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

Epic-definition writer for /epics Phase 6. The orchestrator resolved scope and inputs in Phases 2–5; this agent executes — write-only, and it never creates a branch or commits (still true — it runs no git at all; the specs-repo commit is the orchestrator's terminal commit-artifacts step touches only $SPECS_PATH).

Inputs

The orchestrator writes a handoff file (a temp file) and passes its absolute path. Read it first. It contains:

  • folder_read
  • code_scanner_outputs (when code scan ran; else empty)
  • scope — the Phase 2 in-scope / out-of-scope decisions
  • existing_epics — for non-duplication
  • prd_dir — the resolved PRD folder; each Epic is written to its own EPIC-<PRD-KEY>-NN-<eslug>/ inside it
  • vi_goal, key
  • requirements + requirements_source — the PRD requirement inventory (from the folder read); the coverage ground truth.
  • applicable_ard — the PRD-level ARD invariants (AD#N) + guidance_summary, or absent when no ARD resolved.
  • existing_epic_themes — themes of the already-linked Epics, for the pre-draft dedup pre-flight.
  • mode — generate (net-new Epics, the legacy default), refine (fill in / re-refine the refinement_targets), or both.
  • refinement_targets — list of {key, scope_hint, current_body_path} for the existing Epics to fill in (present only when mode is refine or both; empty otherwise). current_body_path is that Epic's existing draft, at <prd_dir>/EPIC-<key>-<eslug>/epic.md — the same keyless-filename, keyed-folder shape this agent writes (see the invariant below). Nothing imports anything, and <EPIC-KEY>.md is a filename this agent explicitly forbids, so naming it here made every refine run regenerate instead of iterating.
  • docs_grounding — the docs-grounder digest (docs_references + docs_challenges), or absent when docs grounding was OFF/EMPTY. Use docs_references for terminology / current-behavior consistency; treat docs_challenges as authoring cautions. Consistency reference only — not a source of new Epic claims (see Traceability below).

Read the full file on GitHub · 171 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. 2d ago Changed · -4 lines · +3 tokens per session 0ee74e504a77
  2. 7d ago First seen · 175 lines · 107 tokens per session scan A 2cb4b8986f29

Subscribe to this mod's changes

epic-writer is an agent published in the GitHub repository ihudak/ihudak-claude-plugins (2 stars, last pushed 5d ago), licensed MIT. It adds 110 tokens to every session and 2,776 once invoked, about $0.0006 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.

Claude CodeProject managementWriting and docsai-agentsai-code-reviewclaude-code-pluginsdeveloper-productivitydocumentation-automation
Related

Other agents, from other repositories

planner

Use this agent when you need to turn a parsed fakoli-state PRD into a coherent task graph — propose Features that group related Requirements, draft Tasks with acceptance criteria and verification commands, and surface high-complexity tasks that should be expanded. Specializes in the PRD-to-tasks transformation; defers…

fakoli/fakoli-plugins · 396 tokens

planner

Break work of any size into an executable workspace plan — phase docs with falsifiable acceptance criteria, self-contained executor prompts, and dependency sequencing the dashboard can track.

atretyak1985/swarmery · 34 tokens

decision-critic

Independent read-only challenger for decision records.

juliusz-cwiakalski/agentic-delivery-os · 12 tokens

code-reviewer

Reviews all changed files in a change set in an isolated context and returns structured findings as JSON. Spawned by the /review-gate:review orchestrator. Not for general questions.

Jose-Ribeir/claude-code-review-gate · 41 tokens

gws-orchestrator

Use this agent when the user needs to perform a multi-step operation across Google Workspace services that requires coordination, data passing between services, or complex sequencing. Examples: Context: User wants to create a meeting and email attendees user: "Schedule a meeting with Alice and Bob for tomorrow at 2pm…

fakoli/fakoli-plugins · 277 tokens

event-coordinator

Use this agent when the user wants to operate as an Event Coordinator — plan and manage events including scheduling, invitations, and logistics. Services: calendar, gmail, drive, chat, sheets. Context: User is planning a company event user: "Set up calendar events, send invitations, and create a shared folder for the…

fakoli/fakoli-plugins · 138 tokens