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 commands/slackapi/slack-skills-plugin/standupgit clone --depth 1 https://github.com/slackapi/slack-skills-pluginWhat 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.00011 | $0.00305 |
| Opus 5 | $0.00005 | $0.00152 |
| Sonnet 5 | $0.00002 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
standup 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 3d 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.
What it actually says
-
Use
slack_read_user_profile(with no user_id) to get the current user's profile information, including their user ID and display name. -
Search for the user's recent messages using
slack_search_publicwith the filterfrom:<@USER_ID>andafter:set to yesterday's date. This captures messages from the last working day. -
Review the messages found and categorize them into standup themes:
- What I worked on — Topics, projects, or tasks the user discussed or contributed to
- What I'm working on next — Any mentions of upcoming work, plans, or follow-ups
- Blockers — Any questions asked that went unanswered, issues raised, or explicit mentions of being stuck
-
For messages in threads, use
slack_read_threadto get the full context so you can accurately describe what the user contributed. -
Format the standup as:
**Standup for <display name> — <today's date>** **Done:** - Item 1 - Item 2 **Doing:** - Item 1 **Blockers:** - None / Item 1 -
Present the standup to the user for review. They can edit, adjust, or ask you to post it to a specific channel.
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.
- 3d ago First seen · 33 lines · 11 tokens per session scan A 4d7dfa8c9716
standup is a command published in the GitHub repository slackapi/slack-skills-plugin (113 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 305 once invoked, about $0.0001 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 commands, from other repositories
check
Check for available updates to tracked repositories and installed skills without applying changes.
status
Show the current state of skillshare: source, tracked repositories, targets, and versions.
build
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
webperf
Run a web performance audit via the web-performance-auditor persona.
spec
Start spec-driven development — write a structured specification before writing code.
init
First-time setup. Auto-detects installed AI CLIs and configures targets.