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 Lifecycle-Innovations-Limited/claude-ops --skill vipgit clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-opsWrote 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/lifecycle-innovations-limited/claude-ops/vip)<a href="https://agentmods.dev/skills/lifecycle-innovations-limited/claude-ops/vip"><img src="https://agentmods.dev/badge/skills/lifecycle-innovations-limited/claude-ops/vip/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/lifecycle-innovations-limited/claude-ops/vip"><img src="https://agentmods.dev/badge/skills/lifecycle-innovations-limited/claude-ops/vip.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00030 | $0.01730 |
| Opus 5 | $0.00015 | $0.00865 |
| Sonnet 5 | $0.00006 | $0.00346 |
| Haiku 4.5 | $0.00003 | $0.00173 |
Grade A, and why
vip 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 9d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ops:vip — VIP List
Load ops-rules before acting. Public repo (no personal data). Outbound: one draft → one approval → one send. If AskUserQuestion / Workflow are missing, follow Rule 10 in ops-rules (Hermes: numbered options / two-turn Telegram card; delegate_task).
The priority layer over every inbox. VIPs are checked FIRST in any sweep, answered first, drafted with extra care, and never buried in a bulk digest.
Scope (deliberately narrow)
This skill does four things and nothing else:
- Enforce the list — VIP senders rank ahead of everything else in every sweep.
- Require FULL context before answering or drafting for a VIP: the whole thread, every account on that channel, both directions, plus the ledger brief.
- Order triage output by tier.
- Suggest additions when the signals below appear.
It does not read histories for their own sake, does not draft unasked, and does not open a second channel just because one record is open. A tier edit is metadata only. Tagging someone is never an instruction to sweep their history.
Configuration
Nothing here is machine-specific. Every value resolves from userConfig, an env
var, or $HOME.
| userConfig key | Env override | Default | Meaning |
|---|---|---|---|
vip_list_path |
VIP_LIST_PATH |
$HOME/.claude-ops/state/vip-list.json |
Tier data + why/register notes |
vip_max_tier |
VIP_MAX_TIER |
2 |
Highest tier treated as VIP |
vip_suggest_enabled |
— | true |
Emit VIP candidate suggestions |
vip_volume_days |
— | 30 |
Window for the volume signal |
vip_volume_min |
— | 12 |
Two-way messages that trip volume |
relations_cli |
RELATIONS_CLI |
$HOME/.claude-ops/relations/bin/relations-cli |
Shared ledger CLI (see relations) |
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.
- 9d ago First seen · 146 lines · 30 tokens per session scan A 590cf0d28249
vip is a skill published in the GitHub repository Lifecycle-Innovations-Limited/claude-ops (189 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 1,730 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
meeting-agenda-optimizer
Designs effective meeting agendas, reduces meeting waste, and creates structured formats for recurring meetings. Analyzes meeting patterns to recommend which meetings to keep, combine, or eliminate.
release-notes
Generate and publish concise, evidence-based notes in the body of the latest existing GitHub Release. Use only when the user explicitly invokes $release-notes or explicitly asks to update the latest existing GitHub Release body. Do not invoke for general release planning, changelog, tag, or version tasks.
add-teams
Adds Microsoft Teams connector to a Power Apps code app. Use when sending Teams messages, posting to channels, or integrating with Teams chat.
sys-configure
Configure Claude Octopus — redirects to /octo:setup interactive wizard.
cog-braindump-capture
Capture raw thoughts with automatic domain classification and vault routing.
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.