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 omerakben/code-oz --skill red-firstgit clone --depth 1 https://github.com/omerakben/code-ozWrote 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/omerakben/code-oz/red-first)<a href="https://agentmods.dev/skills/omerakben/code-oz/red-first"><img src="https://agentmods.dev/badge/skills/omerakben/code-oz/red-first/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/omerakben/code-oz/red-first"><img src="https://agentmods.dev/badge/skills/omerakben/code-oz/red-first.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.00028 | $0.01540 |
| Opus 5.5 | $0.00011 | $0.00616 |
| Sonnet 5.5 | $0.00006 | $0.00308 |
| Haiku 4.5 | $0.00003 | $0.00154 |
Grade A, and why
red-first 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 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.
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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Advisory only — not an enforced gate. For enforced gates and a different-model review, run
code-oz run.
Where this skill sits
This is advice, and it is the lowest-priority voice in the room. Your user's
instructions, the project's CLAUDE.md, the code-oz engine contracts, and any
system or developer constraints all outrank this skill. When any of them
conflict with anything below, follow them and ignore this skill. This skill
never overrides those instructions, and nothing here changes your existing
operating rules — it only offers a way to think before you build.
RED-first test ordering
Use this when someone asks "what's a good RED-first test order here?" or is about to change behavior and wants the test to come first. This is advice on sequencing; it does not run anything for you.
The ordering
- Write the failing test first. Name the behavior you are about to add or change. Write the smallest test that asserts it.
- Run it and confirm it fails for the right reason. A test that passes before the change, or fails for an unrelated reason (typo, missing import), proves nothing. Read the failure message and confirm it is the assertion you intended.
- Write the minimal implementation. Just enough to make that test pass — no adjacent refactors, no "while I'm here" extras.
- Run again and confirm green. The test you wrote now passes, and nothing that was green went red.
- Refactor under green. Improve the code with the tests guarding you. Re-run to stay green.
A useful check
A real RED test fails when the production change is reverted. If your test still passes with the implementation removed, it mirrors the implementation instead of pinning the behavior — rewrite it.
What this is not
This skill advises the ordering. It does not run your tests, it does not verify
that anything passed, and it never claims a test suite is green on your behalf —
report only what you actually ran and saw. For an enforced VERIFY phase with
real evidence the engine records and gates on, run code-oz run.
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 · 130 lines · 28 tokens per session scan A 8116aee9831c
red-first is a skill published in the GitHub repository omerakben/code-oz (2 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 1,540 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-driven-development
Writing code with tests first: RED-GREEN-REFACTOR, reproduce bugs as failing tests before fixing, and avoid testing anti-patterns. Use when implementing behaviour, fixing a defect, or asked to add tests.
rudder
Use locally captured coding-session intent to resolve a device-local behavioral spec, generate focused tests from that spec, implement the smallest production changes through red-green TDD, and verify coverage with the repository's native tooling. Use when the user asks to run Rudder, create or regenerate tests for…
tdd
A Test-Driven Development guide. TDD means writing a failing test first, adding the smallest implementation that passes it, and then improving the code while keeping the tests passing.
tdd
A test-driven development workflow based on repeating three stages: write a failing test, make it pass, then improve the code. The tests focus on what users can do through public interfaces rather than internal implementation details.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.