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 neuromechanist/research-skills --skill epic-devgit 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/skills/neuromechanist/research-skills/epic-dev)<a href="https://agentmods.dev/skills/neuromechanist/research-skills/epic-dev"><img src="https://agentmods.dev/badge/skills/neuromechanist/research-skills/epic-dev/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/neuromechanist/research-skills/epic-dev"><img src="https://agentmods.dev/badge/skills/neuromechanist/research-skills/epic-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Memory Poisoning · line 135 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
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.00084 | $0.01746 |
| Opus 5 | $0.00042 | $0.00873 |
| Sonnet 5 | $0.00017 | $0.00349 |
| Haiku 4.5 | $0.00008 | $0.00175 |
Grade A, and why
epic-dev 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.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Epic Development Workflow
Codex entrypoint for the same phased epic workflow exposed to Claude Code as
/epic-dev. Use workflow-reference for command snippets, state shape, and
variation details, then follow this procedure as the execution contract.
Operating Rules
- Execute repository detection, GitHub lookups, worktree setup, tests, commits, PR creation, and cleanup directly when prerequisites are valid.
- Ask before strategic points only: epic plan approval, per-phase implementation plan approval, critical review decisions, and final epic merge.
- Use absolute paths in shell commands. Do not rely on a previous
cd. - Track progress with the active planning tool when available.
- Do not use
codex/branch prefixes. Preferfeature/issue-{N}-...,patch/..., orchore/...per project rules. - Do not use emojis in issues, PRs, commits, or generated state.
- Keep the lead on Sol (or the strongest available model) for epic design,
observation, approvals, supervision, load-bearing verification, and final
synthesis. Use Terra only to elaborate an approved phase architecture, and
Luna for detailed implementation, focused review, and validation. Escalate
unresolved design or high-risk invariants per
agent-fanout. - Semantic line breaks remain the default for prose source, except GitHub issue and pull-request bodies. In GitHub bodies, keep each paragraph on one source line, separate paragraphs with blank lines, and do not insert sentence- or clause-level newlines inside a paragraph.
Phase 0: Repository Detection
- Run
project-detect-repo-configfrom the target repository. - Validate required values before continuing:
INTEGRATION_BRANCHREPO_ROOTCURRENT_BRANCH
- Stop and report the exact error if
ERRORis set or required values are empty. - Validate GitHub CLI access. If
HAS_GH=falseorGH_ERRORis set, tell the user what to fix and stop. - If
HAS_GH_SUBISSUE=false, installgh-sub-issuewithgh extension install agbiotech/gh-sub-issueafter normal approval rules for networked commands. - Read existing state from
.claude/epic.local.mdif present. New Codex runs may continue using that file for compatibility with the Claude command.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 141 lines · 84 tokens per session scan A 957a6346a8ac
epic-dev is a skill published in the GitHub repository neuromechanist/research-skills (45 stars, last pushed 8d ago), licensed BSD-3-Clause. It adds 84 tokens to every session and 1,746 once invoked, about $0.0004 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 skills, from other repositories
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
start-task
Create a feature branch for a backlog task, switch to it, and start implementation. Use when the user says "start task-123", "work on task-123", "implement task-123", or invokes /start-task with a task ID.
github-notification-triage
Triage GitHub notifications and issue/PR queues.
utility-pm-release-conductor
Walk the guided 6-gate release runbook (G0 readiness, G1 adversarial review, G2 version bump and CHANGELOG, G2.5 commit and re-verify, G3 tag and push, G4 post-tag hygiene) via the pm-release-conductor sub-agent. Refuses gate bypasses and tags only the re-verified SHA. Use when cutting a pm-skills release.
github-triage
Triage GitHub issues through a label-based state machine with interactive grilling sessions. Use when user wants to triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
releasing-godot-prompter
Use when cutting a GodotPrompter release or bumping its version — the version-bump sequence, tag-triggered workflow, and the marketplace manifests that must follow.