Borrowing it
Nothing to install: this file belongs to workato-devs/recipe-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/workato-devs/recipe-skills/main/.claude/commands/slack-recipes.mdgit clone --depth 1 https://github.com/workato-devs/recipe-skillsWrote 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/commands/workato-devs/recipe-skills/slack-recipes)<a href="https://agentmods.dev/commands/workato-devs/recipe-skills/slack-recipes"><img src="https://agentmods.dev/badge/commands/workato-devs/recipe-skills/slack-recipes/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/commands/workato-devs/recipe-skills/slack-recipes"><img src="https://agentmods.dev/badge/commands/workato-devs/recipe-skills/slack-recipes.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.00000 | $0.00909 |
| Opus 5 | $0.00000 | $0.00454 |
| Sonnet 5 | $0.00000 | $0.00182 |
| Haiku 4.5 | $0.00000 | $0.00091 |
Grade A, and why
slack-recipes 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slack Recipes Skill
DEPENDENCY: Run
/workato-recipesfirst if not already loaded. This skill requires the base Workato knowledge for triggers, control flow, datapills, and recipe structure.
You are now equipped with Slack-specific knowledge for writing Workato recipes. This skill covers two Slack connectors:
| Connector | Provider | Use Case |
|---|---|---|
| Workbot for Slack | slack_bot |
Interactive bots, slash commands, dialogs, buttons |
| Slack (native) | slack |
Programmatic actions via API-triggered recipes |
Capabilities
With this skill loaded, you can:
- Create recipes with Workbot command triggers and slash commands
- Create recipes that post messages to channels and DMs
- Create recipes with interactive dialogs/modals
- Create recipes with button interactions
- Create recipes that chain to other Workbot recipes
- Create callable recipes using native Slack actions
- Look up users by email, create channels, manage membership
Choosing a Connector
Use Workbot (slack_bot) when the trigger is a user interaction (slash command, button click).
Use Native Slack (slack) when the trigger is an API call, scheduler, or another system.
Slack-Specific Knowledge
Provider
Always use slack_bot (Workbot for Slack), not slack:
"provider": "slack_bot"
Datapill Paths (CRITICAL)
Slack does NOT use the ["body"] wrapper for trigger context:
// CORRECT for Slack trigger context
"path": ["context", "user"]
"path": ["context", "channel"]
"path": ["context", "trigger_id"]
"path": ["parameters", "project_name"]
// For adhoc HTTP responses, body IS used
"path": ["body", "channel", "id"]
Dialog Parameters
Parameters are defined as a JSON string with control types:
text- Single-line input (150 char max)text-area- Multi-line input (3000 char max)select- Dropdown withpick_listoptions
Sending DMs
Target the triggering user's DM:
"channel": "=_dp('{...path:[\"context\",\"user\"]}').gsub('\"','')"
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 · 112 lines · 0 tokens per session scan A 6f3d88f2e782
slack-recipes is a command published in the GitHub repository workato-devs/recipe-skills (18 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 909 tokens. 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.