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.
git 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/edit)<a href="https://agentmods.dev/commands/architawr/claude-bpmn-skill/edit"><img src="https://agentmods.dev/badge/commands/architawr/claude-bpmn-skill/edit/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/architawr/claude-bpmn-skill/edit"><img src="https://agentmods.dev/badge/commands/architawr/claude-bpmn-skill/edit.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.00014 | $0.00192 |
| Opus 5.5 | $0.00006 | $0.00077 |
| Sonnet 5.5 | $0.00003 | $0.00038 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
edit 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 1mo 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 edit a BPMN diagram. Input (file plus the requested change): $ARGUMENTS
First summarize the file to understand it, apply the change to the semantics,
then run layout → validate → lint. Report what changed and the result.
layout is non-destructive by default: on a file that already has a diagram
it preserves the existing layout (including hand-tuned positions and Camunda
multi-diagram sub-process pages) and only syncs it to your edit — pruning shapes
for deleted elements and placing shapes for new ones. Only use layout --rebuild
when the user explicitly wants the whole diagram re-laid-out from scratch.
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.
- 1mo ago First seen · 17 lines · 14 tokens per session scan A 162becd94907
edit is a command published in the GitHub repository architawr/claude-bpmn-skill (8 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 192 once invoked, about $0.0001 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-31.
Other commands, from other repositories
brief
A command that turns a rough request and attached documents into a checked, one-page project brief saved under `briefs/`.
spreadsheet-audit
Perform a 6-step audit of an Excel spreadsheet for formula correctness, formatting consistency, data integrity, boss-auditable simplicity, and spec compliance. Uses the excel-screenshot MCP server tools — no Excel installation required.
discuss
A command that interviews you in five phases and saves a detailed description of a proposed feature or change. EARS is a structured way to write requirements so they can be checked clearly.
sdd
A command that creates three connected planning files for a software feature: requirements, design, and tasks.
config
A command for managing `pipeline.yaml`, a version-controlled file that defines how coding work is carried out and checked.
adr
A command that records important, difficult-to-reverse technical choices as Architecture Decision Records, or ADRs.