Borrowing it
Nothing to install: this file belongs to yogasw/wick. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/yogasw/wick/master/.claude/skills/agent-channel-module/SKILL.mdgit clone --depth 1 https://github.com/yogasw/wickWrote 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/yogasw/wick/agent-channel-module)<a href="https://agentmods.dev/skills/yogasw/wick/agent-channel-module"><img src="https://agentmods.dev/badge/skills/yogasw/wick/agent-channel-module/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/yogasw/wick/agent-channel-module"><img src="https://agentmods.dev/badge/skills/yogasw/wick/agent-channel-module.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.00164 | $0.04536 |
| Opus 5.5 | $0.00066 | $0.01814 |
| Sonnet 5.5 | $0.00033 | $0.00907 |
| Haiku 4.5 | $0.00016 | $0.00454 |
Grade A, and why
agent-channel-module 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 2mo 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 — 411 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Channel Module — wick core
Scope: this skill is for transports under
internal/agents/channels/— Slack, Telegram, and any future channel (Discord, Line, MS Teams, …). Channels are wick-internal: downstream projects never write their own. If you are building a tool, job, or connector, use a different skill.
Activate this skill whenever the user touches a channel transport — creating a new one, refactoring an existing one, fixing event fan-out / approval flow / hot-reload bugs, or editing the registry, setup composer, or shared interfaces. When editing an existing channel, audit it against the rules below and bring it up to spec as part of the change.
Mental model
A channel bridges one external chat surface (Slack thread, Telegram chat, …) to the wick agent pool. It owns:
- Inbound: listening for user messages, access control, meta-command intercept, dispatch to the pool via
SendFunc. - Outbound: posting agent replies (chunked, threaded, with reactions/lifecycle markers as appropriate).
- Approval: surfacing gate approval requests as native UI (Slack buttons, Telegram inline keyboard) and resolving the user's decision back through
ApproveFn. - Hot-reload: applying new credentials without restarting the server, via a
ConfigSource.
The registry (channels.Registry) is the single seam between the server and individual channels. Server constructs each channel with its config alone, hands it to the registry, and the registry auto-wires shared dependencies through optional setter interfaces and fans events out to whichever channels implement the matching receiver.
Applies to (non-exhaustive triggers)
- "Add a new channel for Discord / Line / MS Teams / …"
- "Add a meta-command to Slack / Telegram"
- "Fix event fan-out / approval flow / hot-reload bug in channels"
- Any edit under
internal/agents/channels/<name>/ - Changes to
internal/agents/channels/{channel.go, registry.go, store.go}orinternal/agents/channels/setup/
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.
- 2mo ago First seen · 411 lines · 164 tokens per session scan A 293ce2699d4e
agent-channel-module is a skill published in the GitHub repository yogasw/wick (3 stars, last pushed today), licensed MIT. It adds 164 tokens to every session and 4,536 once invoked, about $0.0007 per session on Opus 5.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-31.
Other skills, from other repositories
open-source
Documentation reference for writing Python code using the browser-use open-source library. Use this skill whenever the user needs help with Agent, Browser, or Tools configuration, is writing code that imports from browseruse, asks about @sandbox deployment, supported LLM models, Actor API, custom tools, lifecycle…
n8n-subworkflows
Build reusable, composable n8n sub-workflows. Use when extracting shared logic, building anything multi-step or reused across workflows, or any workflow over 10 nodes — and whenever the user mentions sub-workflows, Execute Workflow, reuse, shared/common logic, modular workflows, "Define Below" inputs…
n8n-code-tool
Write JavaScript or Python for the n8n Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode) — the AI-agent-callable tool, NOT the workflow Code node. Use when building a Code Tool attached to an AI Agent, writing code that an LLM will invoke, parsing the query input, returning a string result, defining an input schema…
omh-backend
This is an OMH backend workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
api-telemetry
Catalog of OpenTelemetry instrumentation built into framework @cyanheads/mcp-ts-core — spans, metrics, completion logs, env config, runtime caveats, custom instrumentation patterns, and cardinality rules. Use when enabling OTel export, adding custom spans or metrics in services, debugging missing telemetry, looking up…