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 skills/breadchaincoop/labor.fun/slack-formattingnpx skills add BreadchainCoop/labor.fun --skill slack-formattinggit clone --depth 1 https://github.com/BreadchainCoop/labor.funWrote 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/breadchaincoop/labor.fun/slack-formatting)<a href="https://agentmods.dev/skills/breadchaincoop/labor.fun/slack-formatting"><img src="https://agentmods.dev/badge/skills/breadchaincoop/labor.fun/slack-formatting.svg" alt="Measured on agentmods" 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 | $0.00036 | $0.00682 |
| Opus 5 | $0.00018 | $0.00341 |
| Sonnet 5 | $0.00007 | $0.00136 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
slack-formatting 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 4d 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.
This is a copy
100% identical to slack-formatting — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slack Message Formatting (mrkdwn)
When responding to Slack channels, use Slack's mrkdwn syntax instead of standard Markdown.
How to detect Slack context
Check your group folder name or workspace path:
- Folder starts with
slack_(e.g.,slack_engineering,slack_general) - Or check
/workspace/group/path forslack_prefix
Formatting reference
Text styles
| Style | Syntax | Example |
|---|---|---|
| Bold | *text* |
bold text |
| Italic | _text_ |
italic text |
| Strikethrough | ~text~ |
|
| Code (inline) | `code` |
inline code |
| Code block | ```code``` |
Multi-line code |
Links and mentions
<https://example.com|Link text> # Named link
<https://example.com> # Auto-linked URL
<@U1234567890> # Mention user by ID
<#C1234567890> # Mention channel by ID
<!here> # @here
<!channel> # @channel
Lists
Slack supports simple bullet lists but NOT numbered lists:
• First item
• Second item
• Third item
Use • (bullet character) or - or * for bullets.
Block quotes
> This is a block quote
> It can span multiple lines
Emoji
Use standard emoji shortcodes: :white_check_mark:, :x:, :rocket:, :tada:
What NOT to use
- NO
##headings (use*Bold text*for headers instead) - NO
**double asterisks**for bold (use*single asterisks*) - NO
[text](url)links (use<url|text>instead) - NO
1.numbered lists (use bullets with numbers:• 1. First) - NO tables (use code blocks or plain text alignment)
- NO
---horizontal rules
Example message
*Daily Standup Summary*
_March 21, 2026_
• *Completed:* Fixed authentication bug in login flow
• *In Progress:* Building new dashboard widgets
• *Blocked:* Waiting on API access from DevOps
> Next sync: Monday 10am
:white_check_mark: All tests passing | <https://ci.example.com/builds/123|View Build>
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.
- 4d ago First seen · 95 lines · 36 tokens per session scan A dd8eeb788015
slack-formatting is a skill published in the GitHub repository BreadchainCoop/labor.fun (2 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 682 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to slack-formatting, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…