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 agents/yogasw/wick/poolgit clone --depth 1 https://github.com/yogasw/wickWhat 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.00000 | $0.04407 |
| Opus 5 | $0.00000 | $0.02204 |
| Sonnet 5 | $0.00000 | $0.00881 |
| Haiku 4.5 | $0.00000 | $0.00441 |
Grade D, and why
pool scanned grade D with 2 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 yesterday.
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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
| Skills dir | `--add-dir ~/.claude/skills` | Agents can read skill files bundled outside the workspace. Only added when `~/.claude/skills/` exists on disk. The system-prompt path table carves out `~/.claude/skills/**` ( Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
2. rm -rf sessions/<id>/ How it starts
The opening of the file, as written. The whole thing — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pool & Sessions
The pool caps how many agent subprocesses run at once across all sessions, FIFO-queues the rest, kills idle ones, and revives them with --resume when new messages arrive.
A session is what holds the conversation: routing key, agent registry, log files, optional project binding.
::: info Source
Pool: internal/agents/pool/ — pool.go (slot allocation), buffer.go (message buffer), factory.go (build agents).
Session: internal/agents/session/ — session.go (Meta, Create/Load/SetProject), agents.go (per-session AgentEntry).
:::
Mental model
┌──────────────────────────── Pool ────────────────────────────┐
│ │
│ active map ┌──────────────────────────────┐ │
│ (max=2): │ slot 1: sess-A / "default" │ │
│ │ slot 2: sess-B / "reviewer" │ │
│ └──────────────────────────────┘ │
│ │
│ queue: [sess-C, sess-A/"backend"] │
│ │
│ buffers: sess-A → ["msg1", "msg2"] ← drained on grant │
│ sess-D → ["pending..."] ← persisted to │
│ meta.PendingInput│
└───────────────────────────────────────────────────────────────┘
| Knob | Default | What | Source |
|---|---|---|---|
MaxConcurrent |
2 | Subprocess cap across all sessions. | pool.go:159 |
IdleTimeout |
120s | Time without I/O before subprocess kill. Timer pauses while output streams. | pool.go:162 |
KillAfterIdle |
0 | Extra grace seconds after idle timeout. | pool.go:56 |
| Queue | FIFO | Sessions waiting for a slot. | pool.go:38 |
| Revive | automatic | New message → spawn with --resume <cli_session_id>. |
pool.go:264 |
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.
- yesterday First seen · 298 lines · 0 tokens per session scan D 73a9f537be41
pool is an agent published in the GitHub repository yogasw/wick (5 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,407 tokens. A static security scan graded it D with 2 findings (enumerates other installed skills, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
Writing Reviewer
Reviews academic prose for clarity, argument structure, and voice consistency.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.