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 tomzx/agents --skill create-slack-announcementgit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/create-slack-announcement)<a href="https://agentmods.dev/skills/tomzx/agents/create-slack-announcement"><img src="https://agentmods.dev/badge/skills/tomzx/agents/create-slack-announcement/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/tomzx/agents/create-slack-announcement"><img src="https://agentmods.dev/badge/skills/tomzx/agents/create-slack-announcement.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.00061 | $0.02349 |
| Opus 5.5 | $0.00024 | $0.00940 |
| Sonnet 5.5 | $0.00012 | $0.00470 |
| Haiku 4.5 | $0.00006 | $0.00235 |
Grade A, and why
create-slack-announcement 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 today.
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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Slack Announcement
Drafts a Slack announcement in regular markdown so the output can be copied and pasted directly. The announcement is presented inside a code block to preserve formatting during copy. Optionally delegates posting to post-slack-message if the user wants to send it directly, converting the draft to Slack mrkdwn at that point.
Prerequisites
- A topic or context for the announcement (provided inline, from a file, or gathered from recent work)
- If posting directly: post-slack-message skill available, plus
SLACK_TOKENin.env - Apply the shared communication guidelines in
skills/communication-guidelines/SKILL.mdwhen composing the announcement.
Inputs
- topic: the subject of the announcement (e.g., "new deployment process", "API v2 launch", "scheduled maintenance window"). Can be a brief description or a detailed context file.
- audience: who the announcement is for (e.g., engineering team, all-hands, specific channel). Used to calibrate tone and detail level.
- context: optional path to a summary file, GitHub activity file, or notes to draw from. If omitted, the user describes the announcement verbally.
- channel: optional target Slack channel. If provided, the skill can delegate posting to post-slack-message after the user reviews the draft.
- action items: optional list of things recipients need to do (e.g., "update your CLI", "review the PR by Friday").
Markdown Formatting Rules
The user reads and copies this draft in regular markdown, so use standard markdown syntax. Slack mrkdwn is only applied later, when the agent posts the message through the Slack API. Slack does not render markdown headers, so use a bold line on its own instead of #.
| Element | Markdown |
|---|---|
| Bold | **bold text** |
| Italic | *italic text* |
| Strikethrough | ~~strikethrough~~ |
| Link with label | [label](https://example.com) |
| Bare link | https://example.com |
| User mention | @name |
| Channel mention | #channel-name |
| Group mention | @here or @channel |
| Bullet list | - item |
| Numbered list | 1. item |
| Inline code | `code` |
| Code block | ``` code ``` |
| Section header | **Header** on its own line (Slack does not render # headings) |
| Divider | --- on its own line |
| Line break | Blank line between paragraphs |
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.
- today First seen · 282 lines · 61 tokens per session scan A a1f763d6a803
create-slack-announcement is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 2,349 once invoked, about $0.0002 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-10-29.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…