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.
git clone --depth 1 https://github.com/neuromechanist/research-skillsWrote 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/commands/neuromechanist/research-skills/epic-status)<a href="https://agentmods.dev/commands/neuromechanist/research-skills/epic-status"><img src="https://agentmods.dev/badge/commands/neuromechanist/research-skills/epic-status/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/commands/neuromechanist/research-skills/epic-status"><img src="https://agentmods.dev/badge/commands/neuromechanist/research-skills/epic-status.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.00007 | $0.00277 |
| Opus 5 | $0.00003 | $0.00138 |
| Sonnet 5 | $0.00001 | $0.00055 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
epic-status 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 11d 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.
What it actually says
Epic Status
Display the current state of the active epic workflow.
Actions
- Find the state file at
.claude/epic.local.mdin the current repo root (usegit rev-parse --show-toplevelto find it) - If no state file exists, report: "No active epic found in this repository."
- If state file exists, read it and parse the YAML frontmatter
- Display a formatted summary:
Epic: #{epic_issue} - {epic_title}
Integration branch: {integration_branch}
Epic branch: {epic_branch}
Current phase: {current_phase} of {total_phases}
Phases:
[x] Phase 1: {title} (#{issue}, PR #{pr})
[ ] Phase 2: {title} (#{issue}) <- current
[ ] Phase 3: {title} (#{issue})
- Check active worktrees with
git worktree listand show which ones belong to this epic - For the current phase, show its branch and whether a PR exists yet
- Show GitHub links:
https://github.com/{owner}/{repo}/issues/{epic_issue}
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.
- 11d ago First seen · 32 lines · 7 tokens per session scan A 362d44e4d214
epic-status is a command published in the GitHub repository neuromechanist/research-skills (45 stars, last pushed 8d ago), licensed BSD-3-Clause. It adds 7 tokens to every session and 277 once invoked, about $0.0000 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-30.
Other commands, from other repositories
octo-scheduler
Manage the Claude Octopus scheduled workflow runner daemon.
arrange-workspace-flow
Workflow for arranging a workspace: layout, reference source code, business/technical context, ecosystem setup.
workflow-foundation-sprint
Run the Foundation Sprint workflow (2-day strategic-alignment arc producing a Founding Hypothesis).
go
You are the Project Kickstart agent. Your job is simple: find PRDs, validate them, and execute the full implementation pipeline.
feature
Role: Per-feature quality pipeline that takes a story or feature description from zero to a committed, documented, tested, and evaluated implementation. No stage is skipped. No commit happens without the evaluator's approval.
swarm
You are the Swarm Coordination Manager: a disciplined parallel execution engine that decomposes work into independent units, dispatches them to isolated workers, monitors progress, detects conflicts, and aggregates results into a coherent whole. You turn serial bottlenecks into parallel throughput — safely.