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 eric-cielo/moflo --skill reset-epicgit clone --depth 1 https://github.com/eric-cielo/mofloWrote 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/eric-cielo/moflo/reset-epic)<a href="https://agentmods.dev/skills/eric-cielo/moflo/reset-epic"><img src="https://agentmods.dev/badge/skills/eric-cielo/moflo/reset-epic/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/eric-cielo/moflo/reset-epic"><img src="https://agentmods.dev/badge/skills/eric-cielo/moflo/reset-epic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00024 | $0.00545 |
| Opus 5.5 | $0.00010 | $0.00218 |
| Sonnet 5.5 | $0.00005 | $0.00109 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
reset-epic 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.
What it actually says
/reset-epic - Reset Epic Test Data
Fully resets an epic so it can be re-tested from scratch.
Arguments: $ARGUMENTS
Usage
/reset-epic <epic-number> # e.g. /reset-epic 287, to reset that epic for retesting
What It Does
Given an epic issue number, perform ALL of the following:
- Identify stories: Parse the epic body for linked issue numbers
- Close open PRs: Find all open PRs referencing any story number or the epic number. Close them.
- Delete remote branches: Find and delete any remote branches related to the epic (e.g.,
epic/<number>-*,feat/<story>-*,revert/epic-<number>-*) - Delete local branches: Delete any local branches matching the same patterns (skip the current branch)
- Reopen issues: Reopen all story issues and the epic itself if any were closed
- Uncheck task lists: Edit the epic body to uncheck all
- [x]checkboxes back to- [ ] - Clear epic-state memory: Delete all entries in the
epic-statememory namespace for this epic and its stories (keys:epic-<N>,story-<N>for each story). Usemcp__moflo__memory_listwith namespaceepic-stateto find entries, thenmcp__moflo__memory_deletefor each. - Verify clean state: Confirm all stories are OPEN, no related PRs are open, no related branches exist, and epic-state memory is empty
Output
Print a summary table:
Epic #<N> Reset Summary
─────────────────────────
Issues reopened: X
PRs closed: X
Branches deleted: X (remote) / X (local)
Status: CLEAN — ready for retesting
Important
- Never delete
mainor the current branch - Use
ghCLI for all GitHub operations - If a revert of merged code is needed, note it but DO NOT auto-revert (ask the user first)
- This is a destructive operation — confirm with the user before executing if there are merged PRs that might need code reverts
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 · 51 lines · 24 tokens per session scan A 601b4f79c5c8
reset-epic is a skill published in the GitHub repository eric-cielo/moflo (19 stars, last pushed 6d ago), licensed MIT. It adds 24 tokens to every session and 545 once invoked, about $0.0001 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.
Other skills, from other repositories
graduate-project
Graduate a life-crm project into its own /gits dev repo and wire the OKF spine between them. Use when a life-crm project needs its own dev or build space (the move to Claude Code), or the user says graduate this project, spin up a repo for it, give it its own repo, or move it to gits. Scaffolds the repo from…
quick
Execute an ad-hoc task with atomic commits. Skips full plan/review.
matilha-hunt
Use when user is ready to dispatch a wave's subprojects — creates git worktrees and kickoff.md per SP, writes wave-NN-status.md, prints dispatch commands.
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
team-release
Orchestrate the release team — release-manager, qa-lead, devops-engineer, producer — to execute a release from candidate to deployment.