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-documentationnpx skills add brifl/coding-agent-orchestration --skill continuous-documentationgit 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.01036 |
| Opus 5 | $0.00008 | $0.00518 |
| Sonnet 5 | $0.00003 | $0.00207 |
| Haiku 4.5 | $0.00002 | $0.00104 |
Grade A, and why
continuous-documentation 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 2d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
continuous-documentation
Purpose
Run the continuous-documentation workflow in continuous mode until the dispatcher
returns recommended_role: stop (no MAJOR/MODERATE findings remain).
The workflow rotates through four prompt steps in a strict cycle:
prompt.docs_gap_analysis— detect missing documentationprompt.docs_gap_fix— apply targeted gap fixesprompt.docs_refactor_analysis— analyze existing doc qualityprompt.docs_refactor_fix— apply refactors
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-documentation
# 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 documentation 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-documentation flag is required — it activates the
continuous override that ignores normal plan-state routing and selects from the
documentation 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-documentation",
"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.
- 2d ago First seen · 120 lines · 16 tokens per session scan A 2487ab545b69
continuous-documentation 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,036 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.