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 skills/joinwell52-ai/codeflowmu-open/qa-verify-fixnpx skills add joinwell52-AI/CodeFlowMu-open --skill qa-verify-fixgit 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-verify-fix)<a href="https://agentmods.dev/skills/joinwell52-ai/codeflowmu-open/qa-verify-fix"><img src="https://agentmods.dev/badge/skills/joinwell52-ai/codeflowmu-open/qa-verify-fix.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.00037 | $0.00167 |
| Opus 5 | $0.00018 | $0.00084 |
| Sonnet 5 | $0.00007 | $0.00033 |
| Haiku 4.5 | $0.00004 | $0.00017 |
Grade A, and why
qa-verify-fix 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
QA Verify Fix
When to use
Use after DEV reports a fix or PM asks for validation.
Rules
- Check behavior against acceptance criteria.
- Keep failures visible.
- Report gaps.
- Do not approve lifecycle directly.
Required output
Use docs/skills/qa-playbook/verify-fix.md.
Forbidden actions
- Do not treat file existence as behavior verification.
- Do not archive or approve lifecycle.
- Do not hide untested criteria.
Minimal example
Check: manifest JSON parses
Result: pass
Evidence: python -m json.tool
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 · 36 lines · 37 tokens per session scan A 2ef3ccfa0505
qa-verify-fix is a skill published in the GitHub repository joinwell52-AI/CodeFlowMu-open (2 stars, last pushed 12d ago), licensed MIT. It adds 37 tokens to every session and 167 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
agentbro-release
Use when releasing AgentBro from this repository: merging dev/main, bumping versions, updating release notes, tagging, pushing, monitoring GitHub Actions, Homebrew cask publication, or fixing a bad release.
agentbro-pr-merge
Use when reviewing, fixing CI for, approving workflows for, or merging AgentBro pull requests into dev/main, especially external contributor PRs where contributor attribution matters.
source-command-check
跑全套本地校验(前端 lint/test/build + Rust check)。.
oculpm-journal
MCP 도구가 보이면 이 스킬 대신 도구를 쓴다 — journalwrite / planstatus / planupdate 가 경로·파일명·frontmatter 규격을 서버에서 보장한다. 아래는 도구가 없을 때 파일을 직접 쓰는 규격이다.
self-audit
작업을 "완료"라고 보고하기 직전, 스스로 결과를 감사할 때. 커밋/PR 직전 최종 점검에도 사용.
project-inception
Use when kicking off a new project or feature area in an ocul-pm tracked project (.oculpm/ present) — research the stack landscape via web search, then converse with the user (research-backed choices) to settle the optimal spec, and seed a discussion doc, a detailed 3-depth plan (plancreate), EVALS.md done-criteria…