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/runbear-io/aweek/slack-initnpx skills add runbear-io/aweek --skill slack-initgit clone --depth 1 https://github.com/runbear-io/aweekWrote 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/runbear-io/aweek/slack-init)<a href="https://agentmods.dev/skills/runbear-io/aweek/slack-init"><img src="https://agentmods.dev/badge/skills/runbear-io/aweek/slack-init.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.00035 | $0.07905 |
| Opus 5 | $0.00017 | $0.03953 |
| Sonnet 5 | $0.00007 | $0.01581 |
| Haiku 4.5 | $0.00003 | $0.00791 |
Grade A, and why
slack-init 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.
How it starts
The opening of the file, as written. The whole thing — 715 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aweek:slack-init
Bootstrap a Slack app for this project and wire its credentials into
aweek serve so users can chat with the project-level Claude through
Slack. The flow has two phases — both are destructive and confirmation-gated:
- Provision — call Slack's
apps.manifest.create+apps.token.createwith the aweek-branded manifest. This creates a real Slack app inside the user's workspace, returns the Socket-Mode app-level token (xapp-…), the OAuth client credentials, and the OAuth authorize URL the human has to visit to install the app and obtain the bot token (xoxb-…). - Persist — merge the resulting credentials into
.aweek/channels/slack/config.jsonso the embedded listener loads them on the nextaweek servestart. The bot token is paste-back from the workspace OAuth install (which is interactive and lives outside this skill).
This skill is a thin UX wrapper on top of src/skills/slack-init.ts. All
remote Slack writes and disk writes go through the dispatcher — never
shell out to Slack APIs or write .aweek/channels/slack/config.json
directly from the markdown.
The persisted file is gitignored under the repo's .aweek/ rule. The
embedded Slack listener still reads process.env first
(SLACK_BOT_TOKEN, SLACK_APP_TOKEN, optional SLACK_SIGNING_SECRET)
and only falls back to the file — so this skill is only needed when the
user wants on-disk credentials rather than environment-variable injection.
v1 scope: project-level Claude proxy only. Per-subagent Slack apps, slash commands, file uploads, channel-per-agent routing, and direct subagent addressing are explicitly out of scope.
Destructive operation policy
Per project policy, every destructive surface requires explicit
AskUserQuestion confirmation before confirmed: true is passed to the
dispatcher. Both underlying primitives (provisionSlackApp and
persistSlackCredentials) refuse to run without it — do not bypass the
gate.
| Operation | Destructive | Confirmation required |
|---|---|---|
provisionSlackApp (creates a Slack app + Socket-Mode token on Slack's side) |
Yes — durable remote write; old refresh token is invalidated | Yes |
persistSlackCredentials (writes .aweek/channels/slack/config.json) |
Yes — overwrites credentials on disk | Yes |
slackInit (composite — runs both stages) |
Yes | Yes |
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 · 715 lines · 35 tokens per session scan A 844ec0c79e70
slack-init is a skill published in the GitHub repository runbear-io/aweek (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 7,905 once invoked, about $0.0002 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-30.
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…