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/delorenj/ssbnkWrote 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/delorenj/ssbnk/bmad-qa-generate-e2e-tests)<a href="https://agentmods.dev/commands/delorenj/ssbnk/bmad-qa-generate-e2e-tests"><img src="https://agentmods.dev/badge/commands/delorenj/ssbnk/bmad-qa-generate-e2e-tests.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.00026 | $0.00046 |
| Opus 5 | $0.00013 | $0.00023 |
| Sonnet 5 | $0.00005 | $0.00009 |
| Haiku 4.5 | $0.00003 | $0.00005 |
Grade A, and why
bmad-qa-generate-e2e-tests 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 4d 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
@skills/bmad-qa-generate-e2e-tests
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.
- 4d ago First seen · 6 lines · 26 tokens per session scan A e8fe8f4f6472
bmad-qa-generate-e2e-tests is a command published in the GitHub repository delorenj/ssbnk (2 stars, last pushed 4d ago), licensed MIT. It adds 26 tokens to every session and 46 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-09-03.
Other commands, from other repositories
test
Write tests before implementation using Red-Green-Refactor.
two-node-origin-pr-helper
Expert review tool for PRs that add or modify Two Node (Fencing or Arbiter) tests under test/extended/twonode/ in openshift/origin.
expand-test-case
Expand basic test ideas or existing oc commands into comprehensive test scenarios with edge cases in oc CLI or Ginkgo format.
new-e2e-test
Write and validate new OpenShift E2E tests using Ginkgo framework.
review-test-cases
Review test cases for completeness, quality, and best practices - accepts file path or direct oc commands/test code.
paul:verify
Guide manual user acceptance testing of recently built features.