Borrowing it
Nothing to install: this file belongs to pillaiharish/opencode-ollama-steroids. 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/pillaiharish/opencode-ollama-steroids/main/.opencode/skills/test-first-agent-loop/SKILL.mdgit clone --depth 1 https://github.com/pillaiharish/opencode-ollama-steroidsWrote 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/pillaiharish/opencode-ollama-steroids/test-first-agent-loop)<a href="https://agentmods.dev/skills/pillaiharish/opencode-ollama-steroids/test-first-agent-loop"><img src="https://agentmods.dev/badge/skills/pillaiharish/opencode-ollama-steroids/test-first-agent-loop/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/pillaiharish/opencode-ollama-steroids/test-first-agent-loop"><img src="https://agentmods.dev/badge/skills/pillaiharish/opencode-ollama-steroids/test-first-agent-loop.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.00031 | $0.00276 |
| Opus 5.5 | $0.00012 | $0.00110 |
| Sonnet 5.5 | $0.00006 | $0.00055 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
test-first-agent-loop 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 2mo 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
Test First Agent Loop
Use this skill when a prompt requires implementation, review, or signoff.
Builder Requirements
The builder must:
- identify required validation commands before claiming completion;
- run unit tests, build/static generation, smoke checks, domain checks, route checks, browser tests, and security scans when relevant;
- stop feature work when validation fails;
- fix failures only inside approved scope;
- rerun failed commands and the full suite when practical;
- document exact commands, results, failures, fixes, and remaining risks.
Reviewer Requirements
The reviewer must block signoff when:
- validation commands are missing;
- output is summarized without evidence;
- tests are superficial or unrelated;
- generated output changed without review;
- screenshots are missing for UI work that needs browser evidence;
- security/redaction checks were skipped before publication.
Honest Reporting
Use precise language:
passedonly when the command completed successfully;failedwhen the command returned non-zero or produced blocking errors;not runwhen skipped, with a reason;not applicableonly when the category genuinely does not apply.
Never hide failures to make a prompt look complete.
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.
- 2mo ago First seen · 42 lines · 31 tokens per session scan A 02533552733e
test-first-agent-loop is a skill published in the GitHub repository pillaiharish/opencode-ollama-steroids (5 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 31 tokens to every session and 276 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-08-31.
Other skills, from other repositories
implement
Use when an approved plan and task list exist and it is time to turn them into working, tested code — the SDD phase after analyze and before verify. Enforces TDD: a failing test comes before the code that makes it pass, one task at a time, appended to a progress ledger that survives compaction. Delegates test tooling…
test-writing
Writes meaningful tests that actually catch bugs.
dev-tdd
TDD development with Red-Green-Refactor cycle. Use to implement a feature by writing tests BEFORE the code. Trigger automatically when the user asks for TDD, wants to write tests first, mentions "test first", or asks to implement, add, create, fix, correct code, a new feature, a bugfix, or a functionality.
tdd
Verify authorized feature, fix, and refactor work with scoped obligations, regression-first fixes, behavioral checks, characterization baselines, coverage, and lint.
ca-feature
Build an authorized feature from a maintained specification, testable criteria and useful plan, without duplicating user approval.
ca-fix
Fix a confirmed bug: a failing regression test first, then a minimal fix, then the rest of the tdd gates.