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 AILiteracyLab/Claude-Build-Test-Loop --skill skillgit clone --depth 1 https://github.com/AILiteracyLab/Claude-Build-Test-LoopWrote 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/ailiteracylab/claude-build-test-loop/skill)<a href="https://agentmods.dev/skills/ailiteracylab/claude-build-test-loop/skill"><img src="https://agentmods.dev/badge/skills/ailiteracylab/claude-build-test-loop/skill/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/ailiteracylab/claude-build-test-loop/skill"><img src="https://agentmods.dev/badge/skills/ailiteracylab/claude-build-test-loop/skill.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.00058 | $0.09954 |
| Opus 5.5 | $0.00023 | $0.03982 |
| Sonnet 5.5 | $0.00012 | $0.01991 |
| Haiku 4.5 | $0.00006 | $0.00995 |
Grade A, and why
devtest scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| **API/Backend** | Expected request/response pairs, status codes, data shapes | HTTP requests (curl, fetch, Playwright API calls), response validation | How it starts
The opening of the file, as written. The whole thing — 466 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design-Test Skill
A general-purpose three-agent feedback loop. The user (Designer) sets the spec, one agent (Builder) implements it, another agent (Tester) validates the result against the spec, and a third agent (Supervisor) monitors for frozen agents and stalled handoffs. They iterate until the Tester confirms the implementation matches. This process applies to any digital function — not just visual design.
Roles
| Role | Who | Responsibility |
|---|---|---|
| Designer | The human user | Defines the spec — what "correct" looks like. Has final say. |
| Builder | Agent teammate | Implements and refines the code/system to match the Designer's spec. |
| Tester | Agent teammate | Validates the result against the spec using appropriate testing methods. Reports discrepancies or approves. |
| Supervisor | Agent teammate | Monitors Builder and Tester every 3 minutes. Detects frozen agents, stalled handoffs, and tasks that should have been marked done. Nudges agents to continue or escalates to the team lead. |
Workflow
Designer provides spec
|
v
Builder implements (Round 1)
|
v
Tester validates against spec (Round 1)
|
Match? --PASS--> Team lead validates evidence --> Done! Report to Designer
|
CONDITIONAL PASS? --> Team lead presents minor issues to Designer
| |
| Accept? --YES--> Done!
| |
| NO (continue iterating)
| |
FAIL <---------------+
|
v
Tester sends feedback to Builder
|
v
Builder checkpoints, revises (Round N), notifies Tester
|
v
(loop back to Tester - Round N)
[Supervisor monitors every 3 min throughout]
[Builder & Tester check Supervisor liveness every 3 rounds]
What Can Be Spec'd and Tested
This skill is not limited to visual design. The Designer can provide any kind of spec:
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.
- 1mo ago First seen · 466 lines · 58 tokens per session scan A 97001d06a698
devtest is a skill published in the GitHub repository AILiteracyLab/Claude-Build-Test-Loop (4 stars, last pushed 7mo ago), licensed MIT. It adds 58 tokens to every session and 9,954 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
goal-test
A local experiment for testing a goal command that keeps an AI coding session working until a stated condition is judged complete. It uses a separate language model to evaluate the conversation after each assistant turn.
loop-test
A local experiment for designing repeating checks with Claude Code’s loop command. It covers both fixed intervals and checks that schedule themselves again after each run.
journey-simulation
Use when caller wants to observe how a stranger encounters a flow, artifact, or sandbox — triggers like "simulate a user journey", "test our onboarding / checkout / signup", "will my ICP convert", "how does a cold reader experience this README", "first-time user test", "cognitive walkthrough", or any request to…
remote
Check what CI on the origin says about this repo's open pull/merge requests, then diagnose and fix the red ones on their own branches. Reads the forge, reproduces locally, pushes fixes to the request's branch — never to the default branch.
accessibility-checks
Use when verifying accessibility (WCAG 2.2 AA) of a rendered UI in a real browser before reporting done — the omp-native replacement for the chrome-devtools a11y plugin. Runs a concrete ordered checklist with omp's builtin browser tool (open tab → tab.evaluate DOM query / elementFromPoint / getComputedStyle /…
ui-verify-checks
Use when verifying a frontend UI change in a real browser before reporting done. The canonical 7-check list (real auth → render≠behavior → scroll containment → primary-button reachability → selection-state sync → responsive → console) + environment fail-fast rule (transport-unreachable vs HTTP error distinction) +…