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/wotai-dev/woterclip/initnpx skills add wotai-dev/woterclip --skill initgit clone --depth 1 https://github.com/wotai-dev/woterclipWrote 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/wotai-dev/woterclip/init)<a href="https://agentmods.dev/skills/wotai-dev/woterclip/init"><img src="https://agentmods.dev/badge/skills/wotai-dev/woterclip/init.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.00072 | $0.02073 |
| Opus 5 | $0.00036 | $0.01037 |
| Sonnet 5 | $0.00014 | $0.00415 |
| Haiku 4.5 | $0.00007 | $0.00207 |
Grade A, and why
woterclip-init 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WoterClip Initialization
Initialize WoterClip in the current repository. This creates the .woterclip/ directory with config, persona templates, and corresponding GitHub labels.
Prerequisites
Before starting, verify the gh CLI is ready:
- Run
gh auth status— must exit 0 (installed and authenticated) - Run
gh repo view --json nameWithOwner— must resolve (the current directory is a repo with a GitHub remote) - If either fails, stop and instruct the user:
- Install:
brew install gh(or the platform equivalent) - Authenticate:
gh auth login - Run from a checkout whose
originpoints at GitHub - Re-run
/woterclip-init
- Install:
Initialization Procedure
Step 1: Gather GitHub Context
- Run
gh repo view --json nameWithOwner --jq .nameWithOwnerto resolve the target repo - Run
gh api user --jq .loginto identify the authenticated user - Present findings and ask the user to confirm:
- The repo whose issues drive the heartbeat (default: the current checkout's repo)
- The Board user's GitHub login for @-mentions in comments (pre-filled from
gh api user)
When the confirmed Board user equals the authenticated login (the common single-account setup), warn: GitHub does not notify a user of their own comments, so blocked-escalation @-mentions will not produce notifications — the Board should watch the repo or rely on /woterclip-status. A separate bot/machine account for gh auth avoids this.
Step 2: Choose Persona Preset
Ask the user which persona set to scaffold:
| Preset | Personas Created |
|---|---|
| engineering (default) | Orchestrator, CEO, Backend, Frontend |
| full | Orchestrator, CEO, Backend, Frontend, Infra, QA |
| minimal | Orchestrator, CEO only |
| custom | Orchestrator, CEO + user-specified personas |
For "custom", ask the user to name each persona and its GitHub label.
Step 3: Create GitHub Labels
GitHub labels are flat (no groups). Create the WoterClip labels on the target repo:
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 · 160 lines · 72 tokens per session scan A ae00739f7c44
woterclip-init is a skill published in the GitHub repository wotai-dev/woterclip (57 stars, last pushed 1mo ago), licensed MIT. It adds 72 tokens to every session and 2,073 once invoked, about $0.0004 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
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
local-frontend-check
Smoke-test or verify UI behaviour on the local Jarvis Registry frontend running at http://localhost/gateway. Use for manual regression checks, bug-fix verification, and end-to-end confirmation of specific flows without running the automated test suite.
ppt-review
Read this skill only after current officereview structural output and relevant rendered images exist. Do not use source code, a tool success flag, or the first-slide preview as a substitute for deck evidence.
helmor-debug-operate
Operate, reproduce, and debug a running local Helmor desktop development build through the Tauri MCP bridge. Use when the user asks to use Tauri MCP, towery MCP, the local dev build, the Tauri webview, visual end-to-end validation, UI automation, screenshots, DOM/accessibility snapshots, IPC or log tracing…
review
5-pass structured code review — correctness, security, performance, readability, consistency.