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 Xakki/ai-agents-skills --skill qa-checkgit clone --depth 1 https://github.com/Xakki/ai-agents-skillsWrote 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/xakki/ai-agents-skills/qa-check)<a href="https://agentmods.dev/skills/xakki/ai-agents-skills/qa-check"><img src="https://agentmods.dev/badge/skills/xakki/ai-agents-skills/qa-check/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/skills/xakki/ai-agents-skills/qa-check"><img src="https://agentmods.dev/badge/skills/xakki/ai-agents-skills/qa-check.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.00066 | $0.00575 |
| Opus 5 | $0.00033 | $0.00287 |
| Sonnet 5 | $0.00013 | $0.00115 |
| Haiku 4.5 | $0.00007 | $0.00057 |
Grade A, and why
qa-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 10d 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-check
A quality gate you run before declaring a task done. It is project-agnostic: it discovers what changed, maps that to the project's make targets, runs only the relevant ones, and reports Pass/Fail per check.
Git mechanics follow the git-flow core; this skill only adds the gate behaviour below.
How to run
- Scope by the diff.
git diff --name-only(vs the base/last commit) → decide which check sections apply (backend / frontend / infra / docs). Run only the sections touching changed paths. Everything goes throughmake. - Run the project's checks for that scope (lint → type/static analysis → unit → targeted functional/e2e). See ask-on-first-use for the mapping.
- Report Pass/Fail per item. Green = the command exits
0and introduces no new warnings. Red = stop and fix the root cause, then re-run.
Anti-patterns — never do these to make it "pass"
- Do NOT skip or disable lint / type checks.
- Do NOT mark tests skipped (
@pytest.mark.skip,.skip,xfail, commenting out) without a real, stated reason. - Do NOT use
--no-verify, and never silence failures with|| trueor by discarding stderr. - Do NOT run the whole suite (
make test) unless the user asks — use the targeted form (name=<...>) for the modules you touched. - Do NOT auto-merge or auto-push because checks went green.
ask-on-first-use (per project)
On the first run in a project you don't know its commands. Ask the user (don't
guess) and offer to save the answers to the project's .claude/ (a line in
<project>/CLAUDE.md or a config file) so later runs skip the questions:
- Path/module → make targets mapping (which lint + test targets cover which areas, e.g. backend vs frontend).
- The minimal always-run command (e.g.
make lint). - (optional) Coverage gate — threshold and where it's enforced.
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.
- 10d ago First seen · 47 lines · 66 tokens per session scan A 2e6d8ba95958
qa-check is a skill published in the GitHub repository Xakki/ai-agents-skills (6 stars, last pushed 19d ago), licensed MIT. It adds 66 tokens to every session and 575 once invoked, about $0.0003 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
taiyi-dev
A software-development stage that implements planned tasks using test-driven development, or TDD: write a failing test, make it pass, then improve the code. It checks the task plan, dependencies, file boundaries, and required completion evidence.
taiyi-test
A project workflow skill for verifying an implementation and producing a TEST.md record. TDD means writing a failing test, implementing the change, and then making the test pass; this skill checks that process and other regression cases.
sc-skill
Capture deterministic macOS screenshots for testing, docs, release notes, and marketing assets. Use when asked to automate app screenshots, batch-generate screenshot sets, standardize window sizing/composition, or choose between Peekaboo and native macOS screenshot tooling.
verify-implementation
A workflow that runs a project’s verification skills to produce a report on coding patterns, architecture rules, and project conventions. It is intended for work after implementation, before a pull request, or during code review.
ag-pipeline-issue
Pipeline Issue→SPEC→Build→Verify→Test. Toda GitHub Issue gera SPEC antes de implementar, e toda implementacao e verificada contra a SPEC e testada. Use when starting work on a GitHub Issue.
ag-referencia-tdd
TDD canonico Red-Green-Refactor — pipeline obrigatorio teste-primeiro. Reference skill carregada on-demand pelo modo --tdd da ag-1-construir.