triage-capture

triage-capture is a skill for Claude Code from vergil-project/vergil-claude-plugin. It costs 123 tokens per session (802 once invoked), scanned A, original, MIT.

A capture tool for recording an unplanned idea, bug, or to-do in an intake queue for later review.

In plain words
What is it for?
It is for filing triage items, ideas, or research requests in an organisation-wide queue, where they can later be reviewed and routed.
Why use it?
It prevents useful thoughts from being lost when they are not yet clear enough to become a planned task.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the vergil plugin — 15 skills, 1 agent, 2 hooks shipped together

Good fit It is for filing triage items, ideas, or research requests in an organisation-wide queue, where they can later be reviewed and routed.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vergil-project/vergil-claude-plugin/triage-capture
Install

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.

Any agent
npx skills add vergil-project/vergil-claude-plugin --skill triage-capture
Clone the repo
git clone --depth 1 https://github.com/vergil-project/vergil-claude-plugin

Made for: Claude Code.

Or install vergil, the plugin that ships this one along with the rest of its 15 skills, 1 agent, 2 hooks.

Wrote 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.

agentmods badge for triage-capture

README.md
[![agentmods](https://agentmods.dev/badge/skills/vergil-project/vergil-claude-plugin/triage-capture/github.svg)](https://agentmods.dev/skills/vergil-project/vergil-claude-plugin/triage-capture)
Your own site
<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.

agentmods 80×15 button for triage-capture

Your own site · 80×15
<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>
Per session 123 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 802 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 10d ago against content hash c9cfed5b57d9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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.

skills/triage-capture/SKILL.md · 60 lines

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

  1. 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.
  2. 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.

  3. Write the body to a temp file (no heredocs) — a one-line problem statement and any context the human gave. Add a ## Why line if the intent isn't obvious from the title.

  4. Create the issue:

    vrg-triage-create --kind <triage|idea|research> \
      --title "<concise, specific title>" \
      --body-file <tmpfile>
    

    vrg-triage-create applies the --kind label, files the issue in the org .github by default, and leaves it unlinked (no parent epic) — triage-review routes it into the epic/task model later. Extra labels are optional via --label.

  5. Report the new issue URL and stop. Do not plan, scope, or start work — that is what triage-review and the formal path are for.

Read the full file on GitHub · 60 lines

Changes

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.

  1. 10d ago First seen · 60 lines · 123 tokens per session scan A c9cfed5b57d9

Subscribe to this mod's changes

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.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

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…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

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…

Donchitos/Claude-Code-Game-Studios · 77 tokens

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.

Orkas-AI/Orkas · 5 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens