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.
npx skills add marcusgoll/Spec-Flow --skill epic-scopinggit clone --depth 1 https://github.com/marcusgoll/Spec-FlowWrote 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/skills/marcusgoll/spec-flow/epic-scoping)<a href="https://agentmods.dev/skills/marcusgoll/spec-flow/epic-scoping"><img src="https://agentmods.dev/badge/skills/marcusgoll/spec-flow/epic-scoping/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/skills/marcusgoll/spec-flow/epic-scoping"><img src="https://agentmods.dev/badge/skills/marcusgoll/spec-flow/epic-scoping.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.00000 | $0.01079 |
| Opus 5.5 | $0.00000 | $0.00432 |
| Sonnet 5.5 | $0.00000 | $0.00216 |
| Haiku 4.5 | $0.00000 | $0.00108 |
Grade A, and why
epic-scoping 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Epic Scoping Skill
Interactive question bank-driven scoping for epic workflows.
Purpose
Systematically scope epics with structured AskUserQuestion calls, eliminating ambiguity before planning. Uses centralized question bank to ensure consistent, comprehensive scoping.
When to Invoke
- Always for new epics (via
/epiccommand) - Skip if resuming with
/epic continue
Quick Start
# Load question bank
cat .claude/skills/epic/references/question-bank.md
5-Round Interactive Scoping
Round 1: Initial Scoping (2 questions)
Questions from bank:
initial_scoping.business_goalinitial_scoping.subsystem_selection
AskUserQuestion({
questions: [
questionBank.initial_scoping.business_goal,
questionBank.initial_scoping.subsystem_selection,
],
});
Apply answers to epic-spec.md:
- business_goal →
## Objective>### Business Value - subsystem_selection →
## Subsystems(update Involved field)
Round 2: Scope Refinement (0-4 questions, conditional)
Based on subsystem_selection, ask relevant follow-ups:
const refinementQuestions = [];
if (selectedSubsystems.includes("Backend API")) {
refinementQuestions.push(questionBank.scope_refinement.backend_scope);
}
if (selectedSubsystems.includes("Frontend UI")) {
refinementQuestions.push(questionBank.scope_refinement.frontend_scope);
}
if (selectedSubsystems.includes("Database")) {
refinementQuestions.push(questionBank.scope_refinement.database_scope);
}
if (selectedSubsystems.includes("External integrations")) {
refinementQuestions.push(questionBank.scope_refinement.integration_scope);
}
if (refinementQuestions.length > 0) {
AskUserQuestion({ questions: refinementQuestions });
}
Apply answers:
- backend_scope →
### Backendsection - frontend_scope →
### Frontendsection - database_scope →
### Databasesection - integration_scope →
### Infrastructuresection
Round 3: Success Metrics (2 questions)
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 · 181 lines · 0 tokens per session scan A 3b0ba07ca134
epic-scoping is a skill published in the GitHub repository marcusgoll/Spec-Flow (96 stars, last pushed 23d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,079 tokens. 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 skills, from other repositories
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
aria
Designs the data model, API contracts, and structural foundation of the system.
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
playtest-report
Structured playtest report template, or turn existing playtest notes into structured feedback.
aws-sst-development
SST v4 (Ion) expert for managing AWS resources as code with the Pulumi-backed framework.
autonomous-agent-patterns
Design patterns for building autonomous coding agents, inspired by Cline and OpenAI Codex.