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 vergil-project/vergil-claude-plugin --skill epic-retrospectivegit clone --depth 1 https://github.com/vergil-project/vergil-claude-pluginWrote 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/vergil-project/vergil-claude-plugin/epic-retrospective)<a href="https://agentmods.dev/skills/vergil-project/vergil-claude-plugin/epic-retrospective"><img src="https://agentmods.dev/badge/skills/vergil-project/vergil-claude-plugin/epic-retrospective/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/vergil-project/vergil-claude-plugin/epic-retrospective"><img src="https://agentmods.dev/badge/skills/vergil-project/vergil-claude-plugin/epic-retrospective.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.00113 | $0.01883 |
| Opus 5 | $0.00056 | $0.00941 |
| Sonnet 5 | $0.00023 | $0.00377 |
| Haiku 4.5 | $0.00011 | $0.00188 |
Grade A, and why
epic-retrospective 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 10d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Epic retrospective
Overview
epic-retrospective is the terminal, run-once finishing gate of the epic
lifecycle. Where epic-create opens an epic with a spec + plan and
epic-implement drives its tasks (re-run as many times as the work takes),
epic-retrospective closes it by authoring a single backward-looking record
— retrospective.md — that partners spec.md and plan.md at the documentation
tier. A later reader follows spec → plan → retrospective: what we set out to
do, how we planned it, and honestly how it went.
Its deeper purpose is the delta between what was planned and what was actually done — the check a Gantt chart never circles back to make. A small delta means the planning discipline is working; a large one means the epic taught us something. Either way it is captured, not lost.
The three-skill lifecycle and their invocation cardinality:
| Skill | Runs | Role |
|---|---|---|
epic-create |
once | make the epic exist (spec + plan + bookends) |
epic-implement |
N times | drive the runnable frontier; pause on blockers; resume |
epic-retrospective |
once | the finishing gate every epic passes through |
Canonical convention: vergil-project/.github#40; this skill's own epic:
vergil-project/.github#201.
Preflight
- Confirm you are the USER agent:
vrg-whoami --modemust printuser. If not, stop. - Resolve the epic ref (
<org>/.github#N,#N, or a URL) and read the epic issue. Identify the retrospective task — the epic's retrospective bookend, seeded byepic-createand stamped with theretrospectivelabel (vrg-issue-create --kind retrospective, tooling ≥ 2.1.167). Identify it by that label. Fall back to the title convention (Retrospective: <epic-slug>) only for epics created before the label existed.
The definition-of-done gate
Running this skill is the assertion "the epic is done." The gate mechanically
verifies that assertion — it is the sole enforcement of the retrospective's
terminality (there are no static Blocked-by reflinks; they would not scale
against a dynamic epic):
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.
- 10d ago First seen · 140 lines · 113 tokens per session scan A 0844c7a2ee2a
epic-retrospective is a skill published in the GitHub repository vergil-project/vergil-claude-plugin (2 stars, last pushed 8d ago), licensed MIT. It adds 113 tokens to every session and 1,883 once invoked, about $0.0006 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.