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 yogasw/wick --skill wick-slack-repliesgit 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/wick-slack-replies)<a href="https://agentmods.dev/skills/yogasw/wick/wick-slack-replies"><img src="https://agentmods.dev/badge/skills/yogasw/wick/wick-slack-replies/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/wick-slack-replies"><img src="https://agentmods.dev/badge/skills/yogasw/wick/wick-slack-replies.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00086 | $0.01261 |
| Opus 5 | $0.00043 | $0.00630 |
| Sonnet 5 | $0.00017 | $0.00252 |
| Haiku 4.5 | $0.00009 | $0.00126 |
Grade A, and why
wick-slack-replies 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 8d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing replies that land well in Slack
Slack does not render markdown. It renders mrkdwn, a different syntax that overlaps just enough to be misleading. wick posts your reply text to Slack as-is — there is no markdown-to-mrkdwn conversion in the send path — so whatever you type is what Slack tries to parse.
That single fact causes most bad-looking Slack replies: **bold** arrives as literal asterisks, ## Heading as a literal ##, and a markdown table as a jumble of pipes.
The syntax that differs
| Intent | Markdown (web chat) | mrkdwn (Slack) |
|---|---|---|
| Bold | **bold** |
*bold* |
| Italic | *italic* or _italic_ |
_italic_ |
| Strikethrough | ~~gone~~ |
~gone~ |
| Link | [label](https://x) |
<https://x|label> |
| Heading | ## Title |
none — use *Title* on its own line |
| Table | pipe table | none — use lines or a code block |
| Bullet | - item |
• item (a literal - also reads fine) |
| Inline code | `code` |
`code` (same) |
| Code block | ```lang |
``` — no language tag |
Note the trap in the first two rows: *text* means bold in mrkdwn but italic in markdown. They are not interchangeable.
The practical strategy
You usually do not know for certain which surface a reply lands on, and the same text may be read in both. So write for the intersection rather than switching dialects:
- Prefer plain prose and short paragraphs. They render identically everywhere.
- Skip headings. On Slack a
##is literal noise. If you need a section label, put a short bolded line or just start a new paragraph. - Skip tables for Slack-bound replies. Use a short list of
label: valuelines, or a code block if alignment genuinely matters. - Use
-bullets. They read fine on both. - Keep it short. Slack messages are read in a narrow column, usually on a phone. A wall of text that scans fine in the web chat is unreadable there.
When you know the reply is Slack-only — a channel notification, an alert, a workflow posting to a channel — write native mrkdwn (*bold*, <url|label>) and it will look right.
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.
- 8d ago First seen · 89 lines · 86 tokens per session scan A e2c9dddc4a55
wick-slack-replies is a skill published in the GitHub repository yogasw/wick (5 stars, last pushed yesterday), licensed MIT. It adds 86 tokens to every session and 1,261 once invoked, about $0.0004 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-31.
Other skills, from other repositories
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
omh-code-review
This is a Hermes-native code-review workflow skill.
redteam-web-detail-pack
Routing and boundary guidance for authorized general web application security testing. Use as a web testing router when the attack surface should be dispatched to more specific web vulnerability skills.
android-pentest
A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.
workflow-builder
Load before calling build-workflow. Default path for all single-workflow work: new one-off workflows, existing-workflow edits, verification repairs, and workflow-local data tables. Write or edit a workspace source file, run workflow-sdk validate via workspaceexecutecommand, then call build-workflow with filePath. When…
jikegongyuan-perspective
A writing guide based on GeekPark, a Chinese technology publication and entrepreneur community focused on AI, products, startups, and innovation.