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 darellchua2/opencode-config-template --skill plan-automation-loop-skillgit clone --depth 1 https://github.com/darellchua2/opencode-config-templateWrote 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/darellchua2/opencode-config-template/plan-automation-loop-skill)<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/plan-automation-loop-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/plan-automation-loop-skill.svg" alt="Measured on agentmods" 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.00054 | $0.07982 |
| Opus 5 | $0.00027 | $0.03991 |
| Sonnet 5 | $0.00011 | $0.01596 |
| Haiku 4.5 | $0.00005 | $0.00798 |
Grade C, and why
plan-automation-loop-skill scanned grade C with 1 finding 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 4d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
Each phase = one iteration. Safety blocks `.env`, `node_modules/`, `rm -rf`, `git push --force`. How it starts
The opening of the file, as written. The whole thing — 603 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
I run a fully-automated, phase-by-phase PLAN execution loop with a hard verification gate between phases. I am the "do the whole plan end-to-end, hands-off" skill:
- Resolve the plan from the
/run-planargument (explicit path/glob, or auto-detect from branch). - Discover verification commands once (lint / build / test / e2e) from project manifests.
- For each phase, in order:
- Implement every atomic step in the phase.
- Ensure newly added code has unit tests (generate the missing ones first).
- Run the verification gate: lint → build/typecheck → unit tests → Playwright e2e (frontend only).
- Fix failures with bounded retries (max 3) — never push red.
- On green: record a
— Done:traceability line under each completed step (what was done + fixes applied + files), mark the phase checkbox[x], commit, push.
- Advance to the next phase. Repeat until all phases are done.
- Final validation against the plan's acceptance criteria.
I am the strict, push-per-phase sibling of plan-execution-skill. The difference: that skill
delegates softly and updates progress; I enforce a gate, write missing tests, run e2e, leave a
per-step traceability record, and commit+push every phase. I compose the existing skills rather
than reimplementing them.
When to use me
Use this skill when:
- The user drives a plan run through
/goal(the primary path): e.g./goal "load plan-automation-loop-skill and implement PLAN-*.md" --max-turns 40 --budget 400k. This wraps the skill in the plugin's hard guardrails (auto-resume, token/duration budgets, compaction-survival, evidence-gated completion). - The user types
/run-plan PLAN-*.md(the fallback path — plain command, soft guardrails only, no plugin runtime hooks; use for short/watched runs). - The user says "fully implement the plan", "run the plan to completion", "automation loop".
Trigger phrases:
implement PLAN-*.md/fully implement PLAN/implement the planrun plan to completion/automation loopimplement plan and commit per phase- "implement the plan with full automation"
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.
- 4d ago First seen · 603 lines · 54 tokens per session scan C cf13a61305a8
plan-automation-loop-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 54 tokens to every session and 7,982 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.
mobiai-ios-testing
Use when writing or running tests in an iOS project — unit tests, UI tests, snapshot tests, choosing the right framework.
testing-llm
LLM and AI testing patterns — mock responses, evaluation with DeepEval/RAGAS, structured output validation, and agentic test patterns (generator, healer, planner). Use when testing AI features, validating LLM outputs, or building evaluation pipelines.