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 jxoesneon/Ciel --skill executing-plansgit clone --depth 1 https://github.com/jxoesneon/CielWrote 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/jxoesneon/ciel/executing-plans)<a href="https://agentmods.dev/skills/jxoesneon/ciel/executing-plans"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/executing-plans/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/jxoesneon/ciel/executing-plans"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/executing-plans.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.00025 | $0.00715 |
| Opus 5 | $0.00013 | $0.00358 |
| Sonnet 5 | $0.00005 | $0.00143 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
executing-plans 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 8d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CIEL ADAPTATION: Executing Plans (Plan Lifecycle Management)
This skill dictates how the Orchestrator manages the high-level lifecycle of a written implementation plan (generated by the make-plan skill). It ensures that plans are not blindly executed, but rather critically reviewed and systematically tracked.
Integration Context
Adapted from ~/.agents/skills/executing-plans/. In CIEL, the actual execution of individual tasks within a plan is handled by subagent-driven-development or dispatching-parallel-agents. This skill (executing-plans) acts as the outer loop: the state management and review mechanism for the entire epic.
The Execution Lifecycle
Phase 1: Load and Critical Review (Mandatory Checkpoint)
Before dispatching the first sub-agent, the Orchestrator MUST:
- Read the complete plan file.
- Critical Analysis: Analyze the plan for missing dependencies, circular logic, or unaddressed technical debt.
- Escalation: If the plan has critical gaps or architectural flaws, the Orchestrator MUST halt and escalate to the human user (
ask_user) before beginning execution. Do not attempt to silently patch a fundamentally broken plan.
Phase 2: State Tracking (The Checkbox Protocol)
As tasks are delegated to sub-agents (via subagent-driven-development), the Orchestrator maintains the global state:
- Log the initiation of each task in the MemPalace Diary (
mempalace_diary_write). - Mark tasks as
IN_PROGRESS. - Upon successful verification of a sub-agent's work (Spec + Quality reviews passed), mark the task as
COMPLETED.
Phase 3: Blocker Protocol
STOP executing immediately when:
- A sub-agent reports a fundamental blocker that requires architectural changes to the original plan.
- The
verification-loopfails consistently across multiple sub-agent retries. - Action: Return to Phase 1 (Review) and propose an updated plan to the human user. Do not force through blockers via endless sub-agent loops.
Phase 4: Epic Completion
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.
- 8d ago First seen · 66 lines · 25 tokens per session scan A 236f2b9e3742
executing-plans is a skill published in the GitHub repository jxoesneon/Ciel (1 stars, last pushed 4d ago), licensed Apache-2.0. It adds 25 tokens to every session and 715 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-09-03.
Other skills, from other repositories
surge
Use when a user provides a PRD, spec, or detailed requirements document and needs a full project delivered through iterative expert orchestration — multi-round analyze/research/design/implement/QA cycles with convergence detection. NOT for: single-file edits, quick prototypes, simple Q&A, or tasks without a written…
ai-native-software-dev
Use when the user asks to build, change, modernize, or reconstruct non-trivial software with an AI-native workflow, including greenfield development, work in an existing codebase, or authorized reference-based product reconstruction; also use when lifecycle planning, architecture, implementation, testing, review…
Code Quality Review
Conduct a comprehensive code quality review focused on clean code, architecture, and project standards.
redpolicy-guide
An editorial policy for turning webinar transcripts into self-contained guides. A transcript is a written record of spoken material, while a self-contained guide can be understood without watching the webinar.
write-overview
A workflow for researching and writing a review essay about a project topic when no finished source text exists. It gathers the facts, studies example essays when available and produces the article in a project output folder.
redpolicy-article
An editorial guide for writing comparison articles about services, tools, and products. It defines a consistent entry format covering the name, link, price, description, and notable features.