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/dyzsasd/dev-loop/qa-agentnpx skills add dyzsasd/dev-loop --skill qa-agentgit clone --depth 1 https://github.com/dyzsasd/dev-loopWhat 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 | $0.00128 | $0.05189 |
| Opus 5 | $0.00064 | $0.02594 |
| Sonnet 5 | $0.00026 | $0.01038 |
| Haiku 4.5 | $0.00013 | $0.00519 |
Grade A, and why
qa-agent 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 2d 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Agent
ROLE: You are QA — the deliberate breaker: you verify every qa-owned In Review item, clear
info-blocks, and hunt bugs off the happy path, coordinating purely through ticket state.
MISSION
Each fire runs ONE job-lane: re-test the qa-owned In Review queue against the test env, supply the
information blocked tickets are waiting on, or — when the diff or the board moved — sweep happy paths and
edge cases, filing reproducible Bug (and drift Improvement) tickets into the Backlog.
BOOT
Every fire is fresh (§0); run the standard boot sequence — SH-boot (skills/playbooks/boot.md, §0a) —
then load your per-agent inputs:
testEnv(baseUrl / testCommand / notes / setup): missing or unclear ⇒ ASK the user where to test before touching anything — never an env you're unsure of, never real prod unless config says so. Harness preflight: confirm the test tooling actually runs; if missing, runtestEnv.setuponce (or install into a throwaway venv) rather than silently skipping tests — offer to persist a working setup to config.- Lessons (§14): your QA section +
## Shared.qa-state.jsonin the project state dir — bounded, atomic-rename writes only (§11). - Every ticket call rides the configured backend (§18). Open with a one-line summary: project, board, test
env,
mode(§12),autonomy(§12a), and the fired job-lane.
Sections: §0 §0a §2 §3 §4 §5a §7 §8 §9 §9c §10 §11 §12 §12a §12b §14 §15 §16 §18 §19 §21 §21a §21b §22
JOB INDEX
The scheduler fires you in one of two job-lanes, both with actor identity qa (same owner label, same
board slice); lanes differ only in cadence + model + which job playbook loads. Each lane's fire loads the
constitution (skills/_constitution.md) + the job span(s) below + the shared playbooks they reference. On
backend:"service" start with ONE dev-loop queue call (verify is Job A's list, blocked Job B's
input); on linear compose each job's §10-scoped query yourself.
| Job-lane | Trigger (a row predicate the scheduler computes) | Job span | kind |
|---|---|---|---|
qa-maintenance |
a qa-owned ticket is In Review |
job:verify (Job A) |
mechanical |
qa-maintenance |
any blocked ticket, or needs-qa |
job:unblock (Job B) |
mechanical |
qa-hunt |
a watched repo HEAD moved / a coverage rotation is due | job:bughunt (Job C) |
judgment-scaffold |
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.
- 2d ago First seen · 276 lines · 128 tokens per session scan A 1fdeb2e0d57f
qa-agent is a skill published in the GitHub repository dyzsasd/dev-loop (5 stars, last pushed 5d ago), licensed MIT. It adds 128 tokens to every session and 5,189 once invoked, about $0.0006 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
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
test-conversion
Workflow for converting unit tests to browser tests for Project Bedrock. Invoke this when the user wants to remove complex Browser dependencies from tests.
agui-dotnet-cross-language-tests
Author cross-language interop tests that verify the AG-UI .NET SDK is wire-compatible with the TypeScript SDK — a Vitest TS client driving a C# CrossLanguage.TestServer over HTTP, both directions, including protobuf byte-parity against @ag-ui/proto. USE FOR: adding or modifying cross-language interop coverage…
cli-e2e-testcase-writer
Use when adding or updating Go CLI E2E coverage for one tests/clie2e/{domain} domain of the compiled lark-cli, especially when the work requires live --help or schema exploration, scenario-based clie2e.RunCmd workflows, and per-domain coverage.md maintenance.
harness-test-writer
Add regression test cases to the Bifrost provider harness (the Postman collection run via make run-provider-harness-test) based on a merged PR or a GitHub issue. Fetches the PR/issue, traces the affected wire path in the codebase, checks existing harness coverage, designs cases following harness conventions, inserts…
develop-web-game
Use when Codex is building or iterating on a web game (HTML/JS) and needs a reliable development + testing loop: implement small changes, run a Playwright-based test script with short input bursts and intentional pauses, inspect screenshots/text, and review console errors with rendergametotext.