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-importgit 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-import)<a href="https://agentmods.dev/skills/wotai-dev/woterclip/persona-import"><img src="https://agentmods.dev/badge/skills/wotai-dev/woterclip/persona-import/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-import"><img src="https://agentmods.dev/badge/skills/wotai-dev/woterclip/persona-import.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.00059 | $0.01208 |
| Opus 5 | $0.00030 | $0.00604 |
| Sonnet 5 | $0.00012 | $0.00242 |
| Haiku 4.5 | $0.00006 | $0.00121 |
Grade A, and why
persona-import 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 10d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Import Persona from Paperclip
Convert a Paperclip agent directory into a WoterClip persona. Maps Paperclip's agent structure (SOUL.md, AGENTS.md, HEARTBEAT.md, TOOLS.md) to WoterClip's persona structure (SOUL.md, TOOLS.md, config.yaml).
Prerequisites
.woterclip/config.yamlmust exist (run/woterclip-initfirst)- User must provide the path to the Paperclip agent directory
File Mapping
| Paperclip File | WoterClip Target | What to Import |
|---|---|---|
SOUL.md |
SOUL.md |
Copy as-is — identity, posture, voice |
HEARTBEAT.md |
Append to SOUL.md |
Only the role-specific responsibilities section (bottom). Skip the generic heartbeat procedure (top) — replaced by the plugin's heartbeat skill |
AGENTS.md |
config.yaml + SOUL.md |
Safety rules → append to SOUL.md Boundaries section. Workspace paths → drop. Memory refs → drop |
TOOLS.md |
TOOLS.md |
Copy, replacing Paperclip API references with gh CLI equivalents |
life/, memory/ |
Skip | Claude Code has built-in memory |
Import Procedure
Step 1: Read Source
Ask the user for the Paperclip agent directory path. Read all files present:
SOUL.md(required)AGENTS.md(optional)HEARTBEAT.md(optional)TOOLS.md(optional)
If SOUL.md doesn't exist, stop — this is not a valid Paperclip agent directory.
Step 2: Ask for Persona Details
Ask the user:
- Persona name — e.g., "Backend Engineer" (pre-fill from SOUL.md if obvious)
- GitHub label — e.g.,
backend(must be unique) - Role type —
engineer,orchestrator,analyst, or custom - Model —
opus,sonnet, orhaiku(suggest based on role) - Escalates to — default:
ceo
Step 3: Transform SOUL.md
- Start with the Paperclip
SOUL.mdcontent - From
HEARTBEAT.md: extract the role-specific section (usually the bottom half, after the generic heartbeat steps). Append as a "## Working Style" or "## Role Responsibilities" section - From
AGENTS.md: extract safety rules and boundaries. Append to the "## Boundaries" section - Add a WoterClip-specific "## Quality Checklist" section if not present
- Drop any Paperclip-specific references (workspace paths, PARA memory, budget tracking)
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.
- 10d ago First seen · 120 lines · 59 tokens per session scan A 7bd46bbb2b52
persona-import is a skill published in the GitHub repository wotai-dev/woterclip (57 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 1,208 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.
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.
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.