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 tomeraitz/claude-slack-bridge --skill build-run-plan-flowgit clone --depth 1 https://github.com/tomeraitz/claude-slack-bridgeWrote 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/tomeraitz/claude-slack-bridge/build-run-plan-flow)<a href="https://agentmods.dev/skills/tomeraitz/claude-slack-bridge/build-run-plan-flow"><img src="https://agentmods.dev/badge/skills/tomeraitz/claude-slack-bridge/build-run-plan-flow/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/tomeraitz/claude-slack-bridge/build-run-plan-flow"><img src="https://agentmods.dev/badge/skills/tomeraitz/claude-slack-bridge/build-run-plan-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 6 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 3 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 11 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 61 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 154 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 47 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 50 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00243 | $0.02853 |
| Opus 5.5 | $0.00097 | $0.01141 |
| Sonnet 5.5 | $0.00049 | $0.00571 |
| Haiku 4.5 | $0.00024 | $0.00285 |
Grade A, and why
build-run-plan-flow 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 2mo 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
build-run-plan-flow — configure the /run-plan phase and write the claude-slack-bridge_run-plan wrapper
You run locally inside Claude Code (not via the Slack daemon). All clarifications go through AskUserQuestion. Do not call mcp__claude-slack-bridge__ask_on_slack from this skill — Slack is only the runtime channel for /process itself, not for setup.
This skill is the run-plan-flow phase of /process-setup. By the time it returns, either:
- The user opted in, the inputs were captured, and
.claude/skills/claude-slack-bridge_run-plan/SKILL.mdhas been generated (status:configured); or - The user opted out at Step 1 — no helper skill is written and the caller is told the literal label
run-plan-flow: skip(status:skipped).
Return values the caller needs (printed as a fenced JSON block at the end of the final reply):
status—configuredorskipped.label—run-plan-flow: configuredwhen configured,run-plan-flow: skipwhen skipped.has_existing_run_plan_process—true/false(only present when configured).existing_run_plan_reference— slash command or path to the user's existing run-plan flow (only whenhas_existing_run_plan_process == true).
Do not skip ahead to writing the helper skill until Step 3 has actually captured everything it needs.
Step 1 — does the user want a run-plan step at all?
Ask via AskUserQuestion:
Do you want a run-plan step in your /process workflow? (the run-plan step takes the approved plan doc, implements it in code, commits + pushes the changes, opens a PR for review, and only then hands off to the next step)
Options:
- Yes, set up the run-plan step — continue to Step 2.
- No, skip it — return immediately with
status: "skipped"andlabel: "run-plan-flow: skip". Do not write any files.
Step 2 — does the user already have a run-plan process?
Capture the user's answer here so Step 3 knows which branch to take. Treat this as the working state of the skill — don't ask the same question twice in Step 3, just consume what you recorded here.
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.
- 2mo ago First seen · 197 lines · 243 tokens per session scan A 479e05b3078e
build-run-plan-flow is a skill published in the GitHub repository tomeraitz/claude-slack-bridge (35 stars, last pushed 1mo ago), licensed MIT. It adds 243 tokens to every session and 2,853 once invoked, about $0.0010 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-08-30.
build-run-plan-flow compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| build-run-plan-flowtomeraitz/claude-slack-bridge | Skill | 35 | 1mo ago | MIT | A | 243 | Claude Code |
| slack-expertpersonamanagmentlayer/pcl | Skill | 44 | 14d ago | Apache-2.0 | A | 69 | Claude Code |
| accesspierreraii/claude-slack-bridge | Skill | 1 | 6mo ago | Apache-2.0 | A | 43 | Claude Code |
| configurepierreraii/claude-slack-bridge | Skill | 1 | 6mo ago | Apache-2.0 | B | 56 | Claude Code |
| opik-diagnosecomet-ml/opik-mcp | Skill | 226 | 3d ago | Apache-2.0 | A | 187 | Claude Code |
| llm-wikiCoWork-OS/CoWork-OS | Skill | 542 | today | MIT | A | 27 | Claude Code, Codex |
| simplifyCoWork-OS/CoWork-OS | Skill | 542 | today | MIT | A | 24 | Claude Code, Codex |