Borrowing it
Nothing to install: this file belongs to drujensen/aiagent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/drujensen/aiagent/main/.claude/commands/qa.mdgit clone --depth 1 https://github.com/drujensen/aiagentWrote 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/drujensen/aiagent/qa)<a href="https://agentmods.dev/commands/drujensen/aiagent/qa"><img src="https://agentmods.dev/badge/commands/drujensen/aiagent/qa/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/commands/drujensen/aiagent/qa"><img src="https://agentmods.dev/badge/commands/drujensen/aiagent/qa.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.00023 | $0.00110 |
| Opus 5.5 | $0.00009 | $0.00044 |
| Sonnet 5.5 | $0.00005 | $0.00022 |
| Haiku 4.5 | $0.00002 | $0.00011 |
Grade A, and why
qa 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
Run the full QA workflow for the aiagent project in sequence. Stop on any failure and fix it before continuing.
go fmt ./...
go vet ./...
go mod tidy
go build .
go test ./...
Report:
- Which steps passed
- Any failures with the error output
- What was fixed (if anything needed fixing)
If all steps pass, confirm the project is 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.
- 4d ago First seen · 21 lines · 0 tokens per session scan A 0323010c554c
qa is a command published in the GitHub repository drujensen/aiagent (5 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 110 once invoked, about $0.0001 per session on Opus 5.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-10-03.
Other commands, from other repositories
go-test
Go TDD workflow with table-driven tests.
go-test
Enforce TDD workflow for Go. Write table-driven tests first, then implement. Verify 80%+ coverage with go test -cover.
check-go
Run Go code quality checks including formatting, linting, vetting, and tests.
golang-test-review
Use when reviewing Go test code (new or changed test.go files, test harnesses, fixtures, or test tooling) for a Go-test-expert pass — behavior-over-surface, determinism, parallel-safety, build-tag correctness, and harness reuse. Complements the general code-reviewer with test-specific rigor.
go-test
Go TDD workflow with table-driven tests.
go-test
A Go testing command that follows test-driven development, or TDD: write a failing test, implement the smallest change that passes it, then improve the code.