agentmods.dev

build-process-skill

build-process-skill is a skill for Claude Code from tomeraitz/claude-slack-bridge. It costs 120 tokens per session (3,752 once invoked), scanned A, original, MIT.

A setup tool that creates a `/process` command for a code repository. The command follows configured workflow steps in order, such as reviewing changes and routing issues for correction.

In plain words
What is it for?
Use it to create `.claude/commands/process.md` and connect the repository’s configured development steps into one command.
Why use it?
It removes the need to manually create and connect the repository’s workflow commands. It also avoids overwriting an existing `/process` command unless the user agrees.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths; mentions subagents; names the AskUserQuestion tool.

Part of the full-process plugin — 7 skills shipped together

not rated 35repo 1mo ago A scan SkillSpector: warn 120 tokens original MIT

Good fit Use it to create .claude/commands/process.md and connect the repository’s configured development steps into one command.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tomeraitz/claude-slack-bridge/build-process-skill
View source ↗ tomeraitz/claude-slack-bridge vibki.com
Install

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.

Any agent
npx skills add tomeraitz/claude-slack-bridge --skill build-process-skill
Clone the repo
git clone --depth 1 https://github.com/tomeraitz/claude-slack-bridge

Made for: Claude Code.

Or install full-process, the plugin that ships this one along with the rest of its 7 skills.

Wrote 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.

agentmods badge for build-process-skill

README.md
[![agentmods](https://agentmods.dev/badge/skills/tomeraitz/claude-slack-bridge/build-process-skill/github.svg)](https://agentmods.dev/skills/tomeraitz/claude-slack-bridge/build-process-skill)
Your own site
<a href="https://agentmods.dev/skills/tomeraitz/claude-slack-bridge/build-process-skill"><img src="https://agentmods.dev/badge/skills/tomeraitz/claude-slack-bridge/build-process-skill/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.

agentmods 80×15 button for build-process-skill

Your own site · 80×15
<a href="https://agentmods.dev/skills/tomeraitz/claude-slack-bridge/build-process-skill"><img src="https://agentmods.dev/badge/skills/tomeraitz/claude-slack-bridge/build-process-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 120 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,752 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 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 103
    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 128
    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.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00120 $0.03752
Opus 5.5 $0.00048 $0.01501
Sonnet 5.5 $0.00024 $0.00750
Haiku 4.5 $0.00012 $0.00375

Measured 2mo ago against content hash 6d8ff3f92d17, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

build-process-skill 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.

plugin/skills/build-process-skill/SKILL.md · 220 lines

How it starts

The opening of the file, as written. The whole thing — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.

build-process-skill — write the /process orchestrator command

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's only job is to create .claude/commands/process.md in the current repo. By the time it returns, either:

  • The file has been written (status: configured); or
  • The file already existed and the user chose to keep theirs (status: skipped).

Return values the caller needs (printed as a fenced JSON block at the end of the final reply):

  • status — configured or skipped.
  • path — .claude/commands/process.md when configured; omitted otherwise.

Step 1 — check whether .claude/commands/process.md already exists

If the file does not exist, continue to Step 2.

If it does exist, ask via AskUserQuestion:

.claude/commands/process.md already exists. Overwrite it with the standard scaffold?

Options:

  1. No, keep mine — return immediately with status: "skipped". Do not touch the file.

  2. Yes, overwrite — continue to Step 2.

  3. No, create it under a different name — ask via AskUserQuestion (free-text via "Other"):

    What filename should I use under .claude/commands/? (e.g. process2.md, my-process.md — must end in .md)

    Validate the reply: it must end in .md, contain no path separators, and not collide with an existing file in .claude/commands/. If invalid or colliding, re-ask. Once valid, record the chosen filename as target_filename and continue to Step 2 — substitute the chosen filename for process.md everywhere below, and update the frontmatter name: to match (filename without .md).

Step 2 — write .claude/commands/process.md

Create .claude/commands/ if missing, then write process.md (atomic write: .process.md.tmp → os.replace) with the following scaffold:

Read the full file on GitHub · 220 lines

Changes

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.

  1. 2mo ago First seen · 220 lines · 120 tokens per session scan A 6d8ff3f92d17

Subscribe to this mod's changes

build-process-skill is a skill published in the GitHub repository tomeraitz/claude-slack-bridge (35 stars, last pushed 1mo ago), licensed MIT. It adds 120 tokens to every session and 3,752 once invoked, about $0.0005 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.

mcpmcp-serverslackslack-bot
Related

build-process-skill compared with skills from other repositories

build-process-skill next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
build-process-skilltomeraitz/claude-slack-bridgeSkill351mo agoMITA120Claude Code
slack-expertpersonamanagmentlayer/pclSkill4414d agoApache-2.0A69Claude Code
accesspierreraii/claude-slack-bridgeSkill16mo agoApache-2.0A43Claude Code
configurepierreraii/claude-slack-bridgeSkill16mo agoApache-2.0B56Claude Code
opik-diagnosecomet-ml/opik-mcpSkill2263d agoApache-2.0A187Claude Code
llm-wikiCoWork-OS/CoWork-OSSkill542todayMITA27Claude Code, Codex
simplifyCoWork-OS/CoWork-OSSkill542todayMITA24Claude Code, Codex