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 summarizegit 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/summarize)<a href="https://agentmods.dev/skills/vergil-project/vergil-claude-plugin/summarize"><img src="https://agentmods.dev/badge/skills/vergil-project/vergil-claude-plugin/summarize.svg" alt="Measured on agentmods" 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.00079 | $0.00913 |
| Opus 5 | $0.00039 | $0.00456 |
| Sonnet 5 | $0.00016 | $0.00183 |
| Haiku 4.5 | $0.00008 | $0.00091 |
Grade A, and why
summarize 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 7d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Summarize
Table of Contents
- Overview
- Mode selection
- Common rules
- Mode: decisions
- Mode: operations
- Mode: soc
- Output templates
- Resources
Overview
Produce a concise, structured summary using the canonical protocol for the selected mode. Preserve outcomes, reasoning, and evidence without adding external knowledge.
Mode selection
Select the mode in this order:
- If the user explicitly specifies a mode, follow it.
- If the user uses
Enter SOCorEnd SOC, use soc mode. - If the request centers on decisions, rationale, or alternatives, use decisions mode.
- If the request centers on actions taken, system changes, or outcomes, use operations mode.
- If multiple modes plausibly apply, ask the minimum clarification question: "Which mode: decisions, operations, or soc?"
Common rules
- Base the summary only on the provided input record.
- Do not add external facts, assumptions, or inferred details.
- Call out missing or ambiguous information explicitly.
- Preserve sequence when the order of events matters.
- Keep the output concise and non-narrative.
Mode: decisions
Follow the Summarize Decisions Protocol.
- Required section order: Results, Reasoning, Options Not Chosen.
- Label implicitly converged decisions as implicit.
- Include optional sections only when present in the input.
Mode: operations
Follow the Summarize Operations Protocol.
- Required section order: Actions Taken, Outcomes and Status, Problems Encountered and Solved, Problems Unresolved, Changes and Artifacts, Follow-up Work and New Issues.
- Capture evidence for command-driven actions (commands + minimal output).
- Include timestamps when available; state when none were provided.
- Redact secrets or sensitive data and note the redaction.
Mode: soc
Follow the Summarize Stream of Consciousness Protocol.
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.
- 7d ago First seen · 144 lines · 79 tokens per session scan A 988d2515dc09
summarize is a skill published in the GitHub repository vergil-project/vergil-claude-plugin (2 stars, last pushed 5d ago), licensed MIT. It adds 79 tokens to every session and 913 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…