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/brifl/coding-agent-orchestration/continuous-test-generationnpx skills add brifl/coding-agent-orchestration --skill continuous-test-generationgit clone --depth 1 https://github.com/brifl/coding-agent-orchestrationWhat 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.00016 | $0.01076 |
| Opus 5 | $0.00008 | $0.00538 |
| Sonnet 5 | $0.00003 | $0.00215 |
| Haiku 4.5 | $0.00002 | $0.00108 |
Grade A, and why
continuous-test-generation 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 3d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
continuous-test-generation
Purpose
Run the continuous-test-generation workflow in continuous mode until the
dispatcher returns recommended_role: stop (only [MINOR] test gaps remain).
The workflow rotates through three prompt steps in a strict cycle:
prompt.test_gap_analysis— identify untested code paths (runs every 3rd checkpoint)prompt.test_generation— generate tests for identified gapsprompt.test_review— review generated tests for correctness
Cold starts are handled automatically — the infrastructure initialises the rotation at step 1 when no prior runtime entry exists.
Agent execution protocol
Run one dispatcher step at a time:
# 1. Ask the dispatcher for the next prompt
python3 .codex/skills/vibe-loop/scripts/agentctl.py --repo-root . --format json next --workflow continuous-test-generation
# 2. Read the prompt body from the catalog path returned by the dispatcher
python3 .codex/skills/vibe-prompts/scripts/prompt_catalog.py <prompt_catalog_path> get <recommended_prompt_id>
# 3. Execute the prompt body (do the actual test generation work)
# 4. After execution, record the loop result
python3 .codex/skills/vibe-loop/scripts/agentctl.py --repo-root . --format json loop-result --line "LOOP_RESULT: <json>"
# 5. Repeat from step 1 until recommended_role == "stop"
The --workflow continuous-test-generation flag is required — it activates
the continuous override that ignores normal plan-state routing and selects from
the test generation prompt rotation instead.
In this orchestration source repo, use tools/agentctl.py and tools/prompt_catalog.py
instead; the .codex runtime helper scripts are generated during install.
LOOP_RESULT format
After executing each prompt, emit a LOOP_RESULT JSON line with the dispatcher-required report fields:
{
"loop": "implement",
"result": "ready_for_review",
"stage": "<current_stage>",
"checkpoint": "<current_checkpoint>",
"status": "<current_status>",
"next_role_hint": "implement|review|stop",
"workflow": "continuous-test-generation",
"report": {
"acceptance_matrix": [
{
"item": "<checked behavior>",
"status": "PASS|FAIL|N/A",
"evidence": "<command or file evidence>",
"critical": true,
"confidence": 0.9,
"evidence_strength": "LOW|MEDIUM|HIGH"
}
],
"top_findings": [
{"impact": "MAJOR|MINOR", "title": "[MAJOR|MODERATE|MINOR] ...", "evidence": "...", "action": "..."}
],
"state_transition": {
"before": {"stage": "<current_stage>", "checkpoint": "<current_checkpoint>", "status": "<previous_status>"},
"after": {"stage": "<current_stage>", "checkpoint": "<current_checkpoint>", "status": "<current_status>"}
},
"loop_result": {
"loop": "implement",
"result": "ready_for_review",
"stage": "<current_stage>",
"checkpoint": "<current_checkpoint>",
"status": "<current_status>",
"next_role_hint": "implement|review|stop"
}
}
}
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 123 lines · 16 tokens per session scan A 4ea00feb56cc
continuous-test-generation is a skill published in the GitHub repository brifl/coding-agent-orchestration (20 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 1,076 once invoked, about $0.0001 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
pest-testing
Use this skill for Pest PHP testing in Laravel projects only. Trigger whenever any test is being written, edited, fixed, or refactored — including fixing tests that broke after a code change, adding assertions, converting PHPUnit to Pest, adding datasets, and TDD workflows. Always activate when the user asks how to…
write-vibe-tests
Write or refactor Mistral Vibe tests with proper decoupling. Use when adding behavior coverage, testing ports/adapters, replacing brittle mocks, creating fakes, adding characterization tests before refactors, or changing tests under tests/ for vibe/core, vibe/cli, vibe/acp, tools, config, sessions, skills, hooks, MCP…
composing-matchers
Build compound Gomega assertions by combining matchers — And/SatisfyAll (all pass), Or/SatisfyAny (any pass), Not (negate), WithTransform to map the actual before matching, Satisfy for an ad-hoc predicate, HaveValue to dereference pointers/interfaces, HaveField for struct fields and method results, HaveEach for every…
adding-dbt-unit-test
Creates unit test YAML definitions that mock upstream model inputs and validate expected outputs. Use when adding unit tests for a dbt model or practicing test-driven development (TDD) in dbt.
testing-guide
Design, write, run, and diagnose Synergy tests with Bun, temporary Scope isolation, deterministic fixtures, and behavior-first assertions. Use for TDD, bug regressions, feature tests, migration tests, flaky tests, coverage, package tests, frontend tests, and selecting verification gates.
test
Generate tests and coverage plans. Triggers: "test", "generate tests and coverage plans.", "test skill".