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 0xranx/agentbrief --skill qa-test-and-fixgit clone --depth 1 https://github.com/0xranx/agentbriefWrote 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/0xranx/agentbrief/qa-test-and-fix)<a href="https://agentmods.dev/skills/0xranx/agentbrief/qa-test-and-fix"><img src="https://agentmods.dev/badge/skills/0xranx/agentbrief/qa-test-and-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.00075 | $0.00786 |
| Opus 5 | $0.00037 | $0.00393 |
| Sonnet 5 | $0.00015 | $0.00157 |
| Haiku 4.5 | $0.00007 | $0.00079 |
Grade A, and why
qa-test-and-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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA: Test & Fix
You are running a full QA cycle. Your goal is to find bugs, fix them, and prove the fixes work — all with atomic commits.
Intensity Tiers
Choose based on the scope of changes:
Tier 1: Smoke Test (quick)
For small changes, single files, or quick checks.
- Run existing test suite
- Manually trace the changed code paths
- Check the 3 most likely edge cases
- Report findings
Tier 2: Standard QA (default)
For features, refactors, or anything touching user-facing code.
- Run existing test suite
- Read all changed files, understand the intent
- Test happy path end-to-end
- Test each edge case category (input, state, error, concurrency)
- Write tests for any untested code paths
- Fix found bugs with atomic commits
- Re-run full test suite to verify no regressions
Tier 3: Deep QA (thorough)
For releases, security-sensitive changes, or critical features.
- Everything in Tier 2
- Fuzz inputs with boundary values
- Test error recovery (kill process mid-operation, corrupt data)
- Test concurrent access patterns
- Review all error handling paths
- Performance check (is anything unexpectedly slow?)
- Security check (input validation, auth, data leaks)
QA Process
Step 1: Baseline
# Run existing tests to establish baseline
pnpm test # or npm test, pytest, go test, etc.
Record: X tests passing, Y tests failing, Z tests skipped.
Step 2: Discover
Read the code changes and identify risk areas:
- New code without tests
- Modified code where tests don't cover the change
- Error handling that's never exercised
- Assumptions about input format or state
Step 3: Reproduce & Diagnose
For each potential bug:
- Write the exact reproduction steps
- Confirm the bug exists (test fails or unexpected behavior)
- Trace the root cause (don't guess — read the code)
Step 4: Fix
For each confirmed bug:
- Write a failing test FIRST
- Make the minimal code change to fix
- Verify the test passes
- Commit atomically:
fix: [what was broken and why]
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.
- 8d ago First seen · 102 lines · 75 tokens per session scan A 766f8f40ece5
qa-test-and-fix is a skill published in the GitHub repository 0xranx/agentbrief (45 stars, last pushed 5mo ago), licensed MIT. It adds 75 tokens to every session and 786 once invoked, about $0.0004 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-30.
Other skills, from other repositories
fix-failing-tests
Diagnose a failing test in the googleapis/mcp-toolbox repo and land a fix by reasoning from the actual error: read the failure, reproduce it, shrink it until the cause is forced into the open, then fix the cause. Use this whenever a test or CI job is red, a build breaks after a change, many packages fail at once, or a…
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
verification
Prove that a coding task is actually complete. Use this after meaningful code changes, when tests/builds fail or are skipped, before marking a plan or goal complete, and whenever acceptance depends on runtime, security, recovery, performance, or cross-module evidence.
ulw-qa
This is a Hermes-native ultraqa workflow skill.
ai-discover
Parallel discovery of performance hotspots (perf track) and failure surfaces (bug track) for the auto-improvement loop. Fans out one subagent per hot-path area or failure surface; each returns ONE concrete, behavior-preserving fix candidate (perf) or a reproducing test plus fix (bug). Discovery only — no code changes…
tmux-manual-qa
Run a single manual tmux-based QA scenario for the todo continuation feature against the real CLI (./pi-test.sh) in an interactive TUI. Captures scrollback, asserts deterministic pass/fail count markers, and cleans up test fixtures. Use only for the manual-qa milestone features.