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 agentmods add skills/huntsdesk/ve-kit/gonpx skills add HuntsDesk/ve-kit --skill gogit 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/go)<a href="https://agentmods.dev/skills/huntsdesk/ve-kit/go"><img src="https://agentmods.dev/badge/skills/huntsdesk/ve-kit/go.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 | $0.00045 | $0.01184 |
| Opus 5 | $0.00023 | $0.00592 |
| Sonnet 5 | $0.00009 | $0.00237 |
| Haiku 4.5 | $0.00005 | $0.00118 |
Grade A, and why
go 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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/go — Autonomous Full-Cycle Execution
Execute a complete RIPER cycle from a single command. The agent handles research, planning, review, execution, and validation — stopping only when human judgment is required.
Usage
/go <task description>
Examples:
/go Fix the mobile padding on the pricing page/go Add a loading spinner to the essay submission button/go Add weekly study streak tracking to the dashboard
Safety Guards
These are hard stops that cannot be bypassed:
| Guard | Threshold | What happens |
|---|---|---|
| REVIEW FAIL | Any critical/high finding | Stops, reports findings, waits for user direction |
| Cumulative lines changed | 500+ lines modified across all files | Stops, reports scope, waits for user to approve continuing |
| Scope escalation | During RESEARCH, task is clearly multi-day or architectural | Stops after RESEARCH, reports findings, asks user to confirm scope |
| User input needed | Implementation requires a decision only the user can make | Stops, asks the specific question, resumes after answer |
| Commit | Never auto-commits or auto-pushes | Reports completion, waits for Enter C |
Execution Protocol
Phase 1: RESEARCH
[MODE: RESEARCH]
- Read all files relevant to the task description
- Understand current state, patterns, dependencies
- Log findings to the board via
board_log_activity - Scope check: If the task is clearly larger than expected (3+ files, architectural decisions, multi-day), STOP and report:
"This task is larger than a /go cycle. It touches [X, Y, Z] and requires [architectural decision]. Recommend entering PLAN mode manually. Continue anyway?"
- If scope is reasonable, auto-advance to PLAN
Phase 2: PLAN
[MODE: PLAN]
- Create board tasks with
assigned_agentand acceptance criteria (per/planskill protocol) - Include a
test-runnertask andcode-reviewertask in the plan - Output the implementation checklist
- Auto-advance to REVIEW (existing behavior)
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 First seen · 106 lines · 45 tokens per session scan A d6c77fb12c2d
go is a skill published in the GitHub repository HuntsDesk/ve-kit (2 stars, last pushed 28d ago), licensed MIT. It adds 45 tokens to every session and 1,184 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-08-31.
Other skills, from other repositories
tmux
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
summarize
Summarize or extract text/transcripts from URLs, podcasts, and local files (great fallback for “transcribe this YouTube/video”).
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.
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.