coding-agent-orchestration: Skill for Codex

.codex/skills/continuous-test-generation/SKILL.md

continuous-test-generation is a skill for Codex from brifl/coding-agent-orchestration. It costs 16 tokens per session (1,076 once invoked), scanned A, original, MIT.

An automated loop that finds untested code paths, creates tests for them, and reviews those tests. It uses TDD-style work, where tests help check that code behaves as expected.

In plain words
What is it for?
Use it to identify test gaps, generate tests, and review the generated tests repeatedly until only minor gaps remain.
Why use it?
It reduces the manual effort of finding missing tests and checking whether newly generated tests are correct.

Skill for Codex

Written for Codex: installed under .codex/. Also seen: reads ~/.codex paths; mentions Codex.

This is brifl/coding-agent-orchestration's own configuration. It tells Codex how to work on coding-agent-orchestration itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything coding-agent-orchestration configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 .codex/skills/vibe-loop/scripts/agentctl.py --repo-root . --format json next --workflow continuous-test-generation.

Reuse

Borrowing it

Nothing to install: this file belongs to brifl/coding-agent-orchestration. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/brifl/coding-agent-orchestration/main/.codex/skills/continuous-test-generation/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/brifl/coding-agent-orchestration

Made for: Codex.

Wrote 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.

agentmods badge for continuous-test-generation

README.md
[![agentmods](https://agentmods.dev/badge/skills/brifl/coding-agent-orchestration/continuous-test-generation/github.svg)](https://agentmods.dev/skills/brifl/coding-agent-orchestration/continuous-test-generation)
Your own site
<a href="https://agentmods.dev/skills/brifl/coding-agent-orchestration/continuous-test-generation"><img src="https://agentmods.dev/badge/skills/brifl/coding-agent-orchestration/continuous-test-generation/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.

agentmods 80×15 button for continuous-test-generation

Your own site · 80×15
<a href="https://agentmods.dev/skills/brifl/coding-agent-orchestration/continuous-test-generation"><img src="https://agentmods.dev/badge/skills/brifl/coding-agent-orchestration/continuous-test-generation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,076 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00016 $0.01076
Opus 5.5 $0.00006 $0.00430
Sonnet 5.5 $0.00003 $0.00215
Haiku 4.5 $0.00002 $0.00108

Measured 2mo ago against content hash 4ea00feb56cc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/continuous_test_generation.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.codex/skills/continuous-test-generation/SKILL.md · 123 lines

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:

  1. prompt.test_gap_analysis — identify untested code paths (runs every 3rd checkpoint)
  2. prompt.test_generation — generate tests for identified gaps
  3. prompt.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"
    }
  }
}

Read the full file on GitHub · 123 lines

Files

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.

Changes

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.

  1. 2mo ago First seen · 123 lines · 16 tokens per session scan A 4ea00feb56cc

Subscribe to this mod's changes

continuous-test-generation is a skill published in the GitHub repository brifl/coding-agent-orchestration (22 stars, last pushed 15d ago), licensed MIT. It adds 16 tokens to every session and 1,076 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-30.

Related

Other skills, from other repositories

rust-testing

Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.

affaan-m/ECC · 31 tokens

cpp-testing

Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.

affaan-m/ECC · 34 tokens

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/appserver, vibe/acp, tools, config, sessions, skills…

mistralai/mistral-vibe · 80 tokens

principle-test-behavior-not-implementation

Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.

michael-denyer/pstack-claude · 50 tokens

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…

onsi/gomega · 136 tokens

spec-driven-tests

Rebuild a package's unit test suite around a behavior specification (SPEC.md) derived from the implementation, with every test citing a numbered rule ID. Use when asked to do a spec-driven test rebuild, write a SPEC.md for a package, repeat the state or store spec process (PRs.

tldraw/tldraw · 63 tokens