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 triage-capturegit 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/triage-capture)<a href="https://agentmods.dev/skills/vergil-project/vergil-claude-plugin/triage-capture"><img src="https://agentmods.dev/badge/skills/vergil-project/vergil-claude-plugin/triage-capture/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/triage-capture"><img src="https://agentmods.dev/badge/skills/vergil-project/vergil-claude-plugin/triage-capture.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.00123 | $0.00802 |
| Opus 5 | $0.00062 | $0.00401 |
| Sonnet 5 | $0.00025 | $0.00160 |
| Haiku 4.5 | $0.00012 | $0.00080 |
Grade A, and why
triage-capture 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage capture
Overview
The formal path (brainstorm → spec → epic → tasks) is the preferred on-ramp, but
most work arrives uncurated — a dog-walk epiphany, a "we should probably…", an
"oh, don't forget". This skill is the lossless net: it turns that raw input
into an intake issue with near-zero friction, so nothing is dropped. The issue
sits in the org .github intake queue until triage-review routes it into the
epic/task model.
When to use
Fire whenever the human wants to record something without stopping to plan it: "don't forget to…", "capture this idea", "note a todo", "file an issue for…", "remind me to…", or a stream-of-consciousness riff on an idea to revisit.
Workflow
-
Pick the kind. All intake is filed in the org
.github(one org-wide queue — no per-repo choice); choose the--kind:triage— a problem, bug, or to-do not yet understood; needs diagnosis.idea— a spark or "what if we…"; a seed to expand into a feature/epic.research— an investigation meant to produce a reproducible result.- When unsure, use
triage.
-
Paraphrase. If the input was voice-to-text (run-on, casual, transcription glitches), rewrite the substance into clean prose for the title and body — never paste the raw transcript into a durable issue.
-
Write the body to a temp file (no heredocs) — a one-line problem statement and any context the human gave. Add a
## Whyline if the intent isn't obvious from the title. -
Create the issue:
vrg-triage-create --kind <triage|idea|research> \ --title "<concise, specific title>" \ --body-file <tmpfile>vrg-triage-createapplies the--kindlabel, files the issue in the org.githubby default, and leaves it unlinked (no parent epic) —triage-reviewroutes it into the epic/task model later. Extra labels are optional via--label. -
Report the new issue URL and stop. Do not plan, scope, or start work — that is what
triage-reviewand the formal path are for.
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 · 60 lines · 123 tokens per session scan A c9cfed5b57d9
triage-capture is a skill published in the GitHub repository vergil-project/vergil-claude-plugin (2 stars, last pushed 8d ago), licensed MIT. It adds 123 tokens to every session and 802 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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.