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 wotai-dev/woterclip --skill persona-creategit 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/persona-create)<a href="https://agentmods.dev/skills/wotai-dev/woterclip/persona-create"><img src="https://agentmods.dev/badge/skills/wotai-dev/woterclip/persona-create/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/wotai-dev/woterclip/persona-create"><img src="https://agentmods.dev/badge/skills/wotai-dev/woterclip/persona-create.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.00070 | $0.00932 |
| Opus 5 | $0.00035 | $0.00466 |
| Sonnet 5 | $0.00014 | $0.00186 |
| Haiku 4.5 | $0.00007 | $0.00093 |
Grade A, and why
persona-create 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Persona
Interactively create a new WoterClip persona for this repository.
Prerequisites
Verify .woterclip/config.yaml exists. If not, instruct the user to run /woterclip-init first.
Procedure
Step 1: Gather Persona Details
Ask the user for:
- Name — Display name (e.g., "QA Engineer", "Infra Engineer", "Research Analyst")
- Role — Role type:
engineer,orchestrator,analyst, or custom - Label — GitHub label for routing issues to this persona (e.g.,
qa,infra,research). Must be unique across existing personas. - Escalates to — Which persona to escalate to (default:
ceo) - Model — Runtime model:
opus,sonnet, orhaiku(suggest based on role complexity) - Required tools — Beyond
gh, which tools does this persona need? Executables (e.g.,docker) are verified withcommand -v; MCP tool prefixes (e.g.,mcp__neon,mcp__plugin_playwright_playwright) are verified by in-session tool availability — the heartbeat's tool-validation step handles each kind differently, so list them exactly as named here.
Step 2: Generate SOUL.md
Create a SOUL.md tailored to the persona's role. Use the structure from existing persona templates:
- Identity — One-sentence role description
- Technical Posture — 5-7 principles for how this persona approaches work
- Voice and Tone — Communication style
- Working Style — How to approach tasks
- Boundaries — What this persona does NOT do (reference other personas)
- Quality Checklist — Pre-completion checks
Present the generated SOUL.md to the user for review. Ask if they want to edit any section.
Step 3: Generate TOOLS.md
Create a TOOLS.md listing:
- Required tools (from step 1)
- Common usage patterns for this persona's role
- Optional tools the user might add later
Step 4: Generate config.yaml
Create the persona's runtime config:
name: <Name>
role: <role>
label: <label>
escalates_to: <escalates_to>
required_tools:
- gh
# additional tools from step 1
runtime:
model: <model>
thinking_effort: <high for opus, medium for sonnet/haiku>
max_turns: <300 for opus, 200 for sonnet, 100 for haiku>
enable_chrome: false
timeout: 0
extra_args: []
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 · 108 lines · 70 tokens per session scan A 70974835ceb6
persona-create is a skill published in the GitHub repository wotai-dev/woterclip (57 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 932 once invoked, about $0.0003 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
watch
File sentinel that monitors the working directory for changes and marker comments, then auto-triggers appropriate skills. Poll-based via git diff against the last scan commit. Writes intake items for batch processing and routes marker actions through /do. Use for automatic reactions to file changes; do NOT use for…
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.
marshal
Meta-orchestrator that takes any direction — broad, specific, or vague — and autonomously chains skills and context into actionable work. Gathers context from codebase, docs, and memory. Only asks the user when it genuinely cannot proceed. Single-session orchestrator.
wiki
Markdown-first knowledge base where the LLM acts as librarian. Ingests raw sources, compiles and interlinks topic files, self-maintains an index. No vector DB or embeddings required -- uses LLM-native navigation over structured markdown up to 400K words.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.