epic-validate

epic-validate is a command for Claude Code from affaan-m/ECC. It costs 10 tokens per session (108 once invoked), scanned A, original, MIT.

A command that checks whether an epic issue is ready for its next workflow stage.

In plain words
What is it for?
Use it to verify an epic's stored state, policy checks, dependencies, and readiness.
Why use it?
It catches missing coordination data, incomplete validation, or open dependencies before publishing or handing the epic to reviewers.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node scripts/github-coordination.js validate <issue-number> --repo <owner/repo>.

Part of the ecc plugin — 70 skills, 56 commands, 68 agents, 1 MCP server shipped together

About the project

ECC is a toolkit that organizes and improves how coding agents work through skills, memory, security checks, research practices, and related extensions. It is for developers using agents such as Claude Code, Codex, OpenCode, and Cursor.

affaan-m/ECC · 250,130 stars · on GitHub · ecc.tools

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/affaan-m/ECC
agentmods
npx agentmods add commands/affaan-m/ecc/epic-validate

Made for: Claude Code.

Or install ecc, the plugin that ships this one along with the rest of its 70 skills, 56 commands, 68 agents, 1 MCP server.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/affaan-m/ecc/epic-validate.svg)](https://agentmods.dev/commands/affaan-m/ecc/epic-validate)
Your own site
<a href="https://agentmods.dev/commands/affaan-m/ecc/epic-validate"><img src="https://agentmods.dev/badge/commands/affaan-m/ecc/epic-validate.svg" alt="Measured on agentmods" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 108 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00010 $0.00108
Opus 5 $0.00005 $0.00054
Sonnet 5 $0.00002 $0.00022
Haiku 4.5 $0.00001 $0.00011

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

Security

Grade A, and why

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

commands/epic-validate.md · 23 lines

What it actually says

/epic-validate

Validate a single epic issue before publishing or review handoff.

node scripts/github-coordination.js validate <issue-number> --repo <owner/repo>

What this checks:

  1. Coordination state exists and is parseable.
  2. Validation state is satisfied by policy.
  3. Declared dependencies are closed.
  4. The epic is ready for the next workflow stage.

Compatibility aliases:

  • /quality-gate
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 First seen · 23 lines · 10 tokens per session scan A 894516dd4de6

Subscribe to this mod's changes

epic-validate is a command published in the GitHub repository affaan-m/ECC (250,130 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 108 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-09-03.