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 skills add joinwell52-AI/CodeFlowMu-open --skill qa-regression-checkgit clone --depth 1 https://github.com/joinwell52-AI/CodeFlowMu-openWrote 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/skills/joinwell52-ai/codeflowmu-open/qa-regression-check)<a href="https://agentmods.dev/skills/joinwell52-ai/codeflowmu-open/qa-regression-check"><img src="https://agentmods.dev/badge/skills/joinwell52-ai/codeflowmu-open/qa-regression-check.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.00039 | $0.00172 |
| Opus 5 | $0.00019 | $0.00086 |
| Sonnet 5 | $0.00008 | $0.00034 |
| Haiku 4.5 | $0.00004 | $0.00017 |
Grade A, and why
qa-regression-check 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 7d 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
QA Regression Check
When to use
Use when a change may affect nearby workflows.
Rules
- Define impacted workflows.
- Keep regression scope focused.
- Record gaps honestly.
- Escalate broad audit requests to PM.
Required output
Use docs/skills/qa-playbook/regression-check.md.
Forbidden actions
- Do not expand into full audit unless tasked.
- Do not claim untested workflows are safe.
- Do not mutate lifecycle.
Minimal example
Workflow: skill validation
Why impacted: new SKILL.md folders
Check: quick_validate.py over skills/*
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.
- 7d ago First seen · 36 lines · 39 tokens per session scan A 8899e8f0db8d
qa-regression-check is a skill published in the GitHub repository joinwell52-AI/CodeFlowMu-open (2 stars, last pushed 13d ago), licensed MIT. It adds 39 tokens to every session and 172 once invoked, about $0.0002 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 skills, from other repositories
gentle-ai-bench
Trigger: bench, journey, journeys, driven mode, gentle-ai-bench, journey corpus, j-numbers, bench axis. Author and verify gentle-ai bench journeys; go test ./bench never proves driven execution.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
coding-agents-hooks-authoring
To author, register, and test Rosetta hooks, add a SemanticKind, or debug a hook that won't fire.
ijfw-verify
Use when about to claim completion: 'done', 'fix complete', 'tests pass', 'build succeeded', 'shipped', 'no regressions', 'ready to merge', 'ready to ship'. Iron Law gate requiring fresh verification evidence in the same message as the claim; wires into runtime (verification-gate.js + the ijfwstate MCP tool…
ijfw-tdd
RED-GREEN-REFACTOR enforcement. Use when implementing a feature or bugfix before writing implementation code. Trigger: tdd, test first, red green refactor, /ijfw-tdd.
api-aqa-flow
Workflow for backend API test automation: TMS / Issue Tracker test cases → automated API tests, HITL-gated.