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/channelsgit 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.11993 |
| Opus 5 | $0.00000 | $0.05997 |
| Sonnet 5 | $0.00000 | $0.02399 |
| Haiku 4.5 | $0.00000 | $0.01199 |
Grade A, and why
channels 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 2d 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 — 664 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Channels
A channel is where a message comes from. Wick agents are reachable from four channels at once:
| Channel | Connection | Session key | Source |
|---|---|---|---|
| Slack | Socket Mode (default) or HTTP Event API | thread_ts |
channels/slack/slack.go |
| Telegram | Long polling | tg-<chatID> |
channels/telegram/telegram.go |
| Web UI | Direct HTTP + SSE | UUID minted by wick | internal/tools/agents/ |
| REST (OpenAI-compatible) | HTTP request/response, OpenAI SDK | rest-<conversation> (or fresh UUID) |
channels/rest/rest.go |
All three implement the same Channel interface (channel.go:59) — the pool sees them uniformly via a SendFunc. Wiring is handled by *Registry (not server.go directly); channels/setup/ composers do the one-call boot assembly.
┌──────────┐ ┌────────────┐ ┌────────┐
│ Slack │ │ Telegram │ │ Web UI │
└────┬─────┘ └─────┬──────┘ └───┬────┘
│ │ │
└──────────────┼─────────────┘
▼
Registry.Add (auto-wires deps via setter interfaces)
│
▼
SendFunc (pool.Send)
│
▼
┌──────────┐
│ Pool │ — slot allocation, queue
└──────────┘
│
▼
Provider subprocess
│
▼
AgentEvent ─────► Registry.DispatchAgentEvent ─► channels
::: info Source
Channel interface + types: channels/channel.go.
Registry + fan-out: channels/registry.go.
Setup composers: channels/setup/setup.go.
DB-backed config store: channels/store.go.
Web UI handler: internal/tools/agents/handler.go.
:::
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.
- 2d ago First seen · 664 lines · 0 tokens per session scan A 35e3273ef7e1
channels is an agent published in the GitHub repository yogasw/wick (5 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 11,993 tokens. 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 agents, from other repositories
firecrawl-expert
Expert in Firecrawl API for web scraping, crawling, and structured data extraction. Handles dynamic content, anti-bot systems, and AI-powered data extraction.
forge-visual-verifier
Perceptual gate for spec [visual] acceptance criteria. Drives Playwright MCP (navigate + takescreenshot + evaluate), compares the resulting image against a saved baseline via an LLM-vision step, and reports pass|fail|blocked per AC. Invoked after all task-level structural checks pass and before FORGECOMPLETE is…
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
security-auditor
Security specialist for CrawlForge MCP Server. Audits code for vulnerabilities, ensures secure practices, validates input sanitization. Use PROACTIVELY before deployments and after major changes.
mcp-implementation
MCP server implementation specialist. Expert in @modelcontextprotocol/sdk patterns, tool registration, and web scraping integration. Use for implementing server code, tools, and core functionality.
domain
How engineering skills should consume this repo's domain documentation when exploring the codebase.