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/validategit 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/validate)<a href="https://agentmods.dev/commands/architawr/claude-bpmn-skill/validate"><img src="https://agentmods.dev/badge/commands/architawr/claude-bpmn-skill/validate.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.00012 | $0.00117 |
| Opus 5 | $0.00006 | $0.00059 |
| Sonnet 5 | $0.00002 | $0.00023 |
| Haiku 4.5 | $0.00001 | $0.00012 |
Grade A, and why
validate 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 5d 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 validate the BPMN file at: $ARGUMENTS
Run validate (well-formed XML, every flow node/edge has a shape, no overlapping
shapes) and lint (deadlocks, double execution, stuck-token gateways). Summarize
the findings in plain language and propose concrete fixes. If the user asks,
apply the fixes and re-run both until clean.
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.
- 5d ago First seen · 12 lines · 12 tokens per session scan A 9025f81116a6
validate is a command published in the GitHub repository architawr/claude-bpmn-skill (5 stars, last pushed 3mo ago), licensed MIT. It adds 12 tokens to every session and 117 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
release-now
Create a git tag + GitHub Release for open-pr — an official release if standing on main, an RC if standing on a branch with an open PR (a dev tool specific to this repo, not shipped in the plugin).
vitaecontext-github
Audit or improve GitHub profile and repository SEO.
vitaecontext-vitaegraph
Create, validate, index, or use a private VitaeGraph.
vitaecontext-x
Audit or improve X/Twitter profile and posting strategy.
discuss
5-phase requirements-elicitation interview that produces an EARS-validated context/ .md.
adr
Create an Architecture Decision Record in memory-bank BACKLOG.