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 HuntsDesk/ve-kit --skill plangit clone --depth 1 https://github.com/HuntsDesk/ve-kitWrote 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/huntsdesk/ve-kit/plan)<a href="https://agentmods.dev/skills/huntsdesk/ve-kit/plan"><img src="https://agentmods.dev/badge/skills/huntsdesk/ve-kit/plan/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/huntsdesk/ve-kit/plan"><img src="https://agentmods.dev/badge/skills/huntsdesk/ve-kit/plan.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.01738 |
| Opus 5.5 | $0.00014 | $0.00695 |
| Sonnet 5.5 | $0.00007 | $0.00348 |
| Haiku 4.5 | $0.00003 | $0.00174 |
Grade A, and why
plan 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 11d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PLAN Mode Protocol
You are entering PLAN mode. Follow this protocol exactly.
Step 0: Detect Work Type (3-tier vs flat)
Before generating an implementation checklist, classify the work request. Most invocations are flat — Step 0 is a fast routing check, not a ceremony.
Invoke 3-tier flow (story → design → tasks) when ANY hold:
- Work spans 5+ implementation tasks
- Touches shared infra (DB schema, RLS, auth, billing, deployment pipeline)
- Crosses 2+ services
- Has external stakeholder visibility (founder asked for a named deliverable, or it'll appear in marketing/release notes)
- Requires architectural decision visible to non-engineers (e.g., choosing between competing approaches that have long-term implications)
Use the flat flow (Steps 1-4 below — existing behavior) when:
- Single-thread bug fix, refactor, or feature touching <5 tasks
- One-file change
- Adding a flag, deploying from existing template, routine ops
- Estimable in <4 hours
When in doubt → ask the user with choice-based clarification (ONE multiple-choice question at a time, never a 10-question waterfall):
This looks like substantial work. Should I:
- Create a STORY (with "why" + success metric) + DESIGN RFC (with ripple effects + ADRs) + implementation tasks
- Just create a flat implementation task list (skip story + design — faster, less anchoring)
If 3-tier is selected: invoke project-coordinator to produce the STORY task + DESIGN task per its 3-Tier Decomposition Protocol, THEN return here for Step 2 to decompose the design into implementation tasks. Set design_id: <design_task_id> on each implementation task so reviewers can trace back, and parent_task_id: <design_task_id> for the hierarchy link.
Set the native task_type on every task you create — story, design, task, bug, chore, investigation — plus story_id / design_id for linkage. Don't put the type in the title; legacy tasks that carry a [STORY] / [DESIGN] / [BUG] / [CHORE] / [INVESTIGATION] prefix predate the field. See .claude/rules/agent-board.md § Task Type.
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.
- 11d ago Changed · -2 lines 9806edf84473
- 1mo ago Changed · +3 lines cc555268227c
- 1mo ago Changed · +4 lines 7fa13f278a4f
- 1mo ago First seen · 120 lines · 34 tokens per session scan A 60ff7c6a249f
plan is a skill published in the GitHub repository HuntsDesk/ve-kit (3 stars, last pushed 10d ago), licensed MIT. It adds 34 tokens to every session and 1,738 once invoked, about $0.0001 per session on Opus 5.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
hive.slack-notifications-setup
Set up a Slack notification channel (Sentinel) for a colony by driving the browser — reuse or create the "Hive Sentinel" Slack app from a JSON manifest, install it, capture the bot + app tokens, create/select the channel via the Slack API, and turn Sentinel on so the colony can ping the user on Slack and accept…
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
hive.pdf
Read, write, merge, split, rotate, watermark, encrypt, and OCR PDF files using Python (pypdf, pdfplumber, reportlab, pypdfium2) and command-line tools (poppler-utils, qpdf). Use when the user asks to extract text/tables/images from a PDF, create or modify a PDF, combine or split PDFs, OCR a scanned PDF…
hive.note-taking
Maintain a free-form scratchpad of decisions, extracted values, and open questions so context pruning doesn't lose anything you still need.
vuln-scanner
Audit trending repos for real security vulnerabilities and disclose responsibly - scan and route findings (PVR / dependency PR), re-submit queued advisories, and send armed email disclosures.