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 zernie/vigiles --skill ship-prgit clone --depth 1 https://github.com/zernie/vigilesWrote 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/zernie/vigiles/ship-pr)<a href="https://agentmods.dev/skills/zernie/vigiles/ship-pr"><img src="https://agentmods.dev/badge/skills/zernie/vigiles/ship-pr.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.00015 | $0.00246 |
| Opus 5 | $0.00008 | $0.00123 |
| Sonnet 5 | $0.00003 | $0.00049 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
ship-pr 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 4d 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.
What it actually says
Arguments
$1branch — the branch to open the PR from$2title (optional) — PR title
Steps
Step 1
Run the linter and fix any issues it reports.
Gate — run npm run lint; do not proceed until it passes.
Step 2
Run the test suite. Fix failures and re-run until it is green.
Gate — run npm test (retry up to 3×); do not proceed until it passes.
Step 3
Open the pull request from $1 with title $2 (if provided).
Result
This skill is complete when npm test passes.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago Changed · -2 lines · +15 tokens per session 63c499834f91
- 8d ago First seen · 43 lines · 0 tokens per session scan A a46a20b7bfdd
ship-pr is a skill published in the GitHub repository zernie/vigiles (15 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 246 once invoked, about $0.0001 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-30.
Other skills, from other repositories
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…
review-pr
Perform a comprehensive code review of a pull request.
pr
Analyze changes, detect scope issues, and create a well-structured PR.
validate-changes
Evaluate staged changes using LLM-as-a-Judge before committing.
code-commit
Generate and validate conventional commit messages following the conventionalcommits.org spec. Use whenever the user wants to commit code, mentions commit messages, git commit, or asks to create a commit. Triggers on "commit", "git commit", "conventional", or when reviewing commit message format.
spec-finish
Post-implementation completion workflow for Spec-backed Plans. Use after spec-implement completes to validate, review, create stacked commits, and open a PR via code-pull-request. Triggers only with an active Spec-backed Plan after spec-implement completes, including when the user says "finish", "done", or "complete"…