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/architawr/claude-bpmn-skill/explaingit clone --depth 1 https://github.com/architawr/claude-bpmn-skillWrote 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/architawr/claude-bpmn-skill/explain)<a href="https://agentmods.dev/commands/architawr/claude-bpmn-skill/explain"><img src="https://agentmods.dev/badge/commands/architawr/claude-bpmn-skill/explain.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.1 | $0.00018 | $0.00166 |
| Opus 5 | $0.00009 | $0.00083 |
| Sonnet 5 | $0.00004 | $0.00033 |
| Haiku 4.5 | $0.00002 | $0.00017 |
Grade A, and why
explain 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 6d 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 the bpmn skill to read and explain the BPMN diagram at: $ARGUMENTS
Run the skill's summarize on the file first (it is your source of truth — don't
eyeball raw DI), then explain the process in plain language: the happy path
first, then decision points (what each gateway branches on), parallel work, and
exception / boundary handling. Name real business steps, not element IDs, and
match the user's language. If this looks like a review ("is this correct?", "why
does it hang?"), also run lint and report any control-flow issues.
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.
- 6d ago First seen · 14 lines · 18 tokens per session scan A 4d50dbd903a6
explain is a command published in the GitHub repository architawr/claude-bpmn-skill (5 stars, last pushed 3mo ago), licensed MIT. It adds 18 tokens to every session and 166 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-31.
Other commands, from other repositories
teach
Teach the user a skill or concept inside a persistent teaching workspace. This is a stateful, multi-session request: the user intends to learn the topic over time, and each run builds on the last. The topic is the text after the command (/nitpicker teach rust ownership); with no topic, read the existing workspace and…
_teach-formats
Formats for the three markdown artifacts the teach command writes into docs/lessons/. Lessons, reference documents, and assets are HTML and have no fixed template — their rules live in teach.md.
discuss
5-phase requirements-elicitation interview that produces an EARS-validated context/ .md.
lrn
Execute the /vibeguard:learn command. $ARGUMENTS.
bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
start-1
Claude Code 를 처음 쓰는 PM 이 "설치 → 도구 지도 이해 → CLAUDE.md 로 맥락 주기" 까지 직접 손으로 해보며 익히도록, 한 번에 한 단계씩 끌고 간다.