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 issue-deploygit 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/issue-deploy)<a href="https://agentmods.dev/skills/vergil-project/vergil-claude-plugin/issue-deploy"><img src="https://agentmods.dev/badge/skills/vergil-project/vergil-claude-plugin/issue-deploy.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.00063 | $0.01286 |
| Opus 5 | $0.00032 | $0.00643 |
| Sonnet 5 | $0.00013 | $0.00257 |
| Haiku 4.5 | $0.00006 | $0.00129 |
Grade A, and why
issue-deploy 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Deploy
Run a deployment task to completion and record the result — the act of
taking merged changes and getting them deployed and usable in the environment,
the step between an implementation task (merged) and a validation task
(verified). Deployment is one operational task kind: it follows the shared
operational-task lifecycle
(preflight → preconditions gate → run → record Outcome: → close-on-success /
hold-open-on-failure). Below is the deployment-specific detail.
Sibling skills, deliberately different:
issue-implement |
issue-validate |
issue-deploy (this) |
|
|---|---|---|---|
| Goal | Write code | Verify it works | Make it usable (deploy) |
| Workspace | Worktree + PR | None | None — touches no code |
| Terminal state | PR handoff | SUCCESS/FAILURE comment | SUCCESS/FAILURE comment |
| On failure | Fix in place | File a fix task | Retry (idempotent), then fix task |
If the issue is not deployment-labelled, stop: a validation issue goes to
issue-validate; anything non-operational goes to issue-implement.
Never fabricate a result
If you cannot actually run a step, say so and stop — never fabricate or
partially fake a result. Use whatever means are efficient to run it (sub-agents
encouraged); oversight is front-loaded and at the hard gates, not in a live
transcript (the Front-Loaded Judgment, Trusted Execution doctrine; see
CLAUDE.md). If you hit a problem you cannot resolve, stop and ask.
Preflight
- Confirm you are the USER agent:
vrg-whoami --modemust printuser. - Confirm the issue carries the
deploymentlabel (vrg-gh issue view <N> --json labels). If not, this is the wrong skill. - Read the issue body — a self-contained scaffold: preconditions, deploy steps, acceptance criteria, and a results template.
Preconditions gate — release is a precondition, not your job
Work the issue's Preconditions first. Deployment has one that matters especially:
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 · 105 lines · 63 tokens per session scan A 6661847381d1
issue-deploy is a skill published in the GitHub repository vergil-project/vergil-claude-plugin (2 stars, last pushed 5d ago), licensed MIT. It adds 63 tokens to every session and 1,286 once invoked, about $0.0003 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-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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…