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 make-plangit 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/make-plan)<a href="https://agentmods.dev/skills/jxoesneon/ciel/make-plan"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/make-plan/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/make-plan"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/make-plan.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.00016 | $0.00705 |
| Opus 5 | $0.00008 | $0.00352 |
| Sonnet 5 | $0.00003 | $0.00141 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
make-plan 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CIEL ADAPTATION: Make-Plan (The Strategic Layer)
This skill serves as CIEL's "Strategic Layer," transforming high-level design specs into detailed, phased implementation plans. It ensures that every action is grounded in evidence and documentation.
Integration Context
Adapted from ~/.agents/skills/make-plan/. This skill is the bridge between brainstorming (Design) and do (Execution). It mandates "Documentation Discovery" as the first step of any implementation.
Orchestration Logic
1. Spec Ingestion
The plan MUST start by reading the approved design spec from docs/ciel/specs/. Every phase of the plan must map back to a requirement or architectural choice in the spec.
2. Phase 0: Documentation Discovery (MANDATORY)
Before any implementation tasks are defined, CIEL must:
- Use
grep_searchandmempalace-rsto find relevant internal examples. - Use
documentation-lookuporweb_fetchfor external API signatures. - Output a "Source of Truth" summary: exact file paths, API signatures, and copy-ready patterns.
3. Phased Execution Design (Blueprint)
Break the implementation into Task Atomic Units (TAUs):
- Each task should take 5-15 minutes of agent time.
- Tasks must be sequentially independent where possible.
- Each task MUST specify:
- Files: Exact paths to create, modify, or read.
- Test Plan: Specific test commands and expected output.
- Commit Mandate: Explicit commit message for the task.
🚫 The "No Placeholders" Mandate
The following patterns are Plan Failures and are strictly prohibited:
- "Refine implementation logic to align with Ciel 1.0 standards.", "TBD", or "Implement later."
- "Add appropriate validation" (must specify the exact validation logic).
- "Similar to Task N" (must repeat the instructions; tasks may be executed out of order).
- "Write tests" (must include the actual test code snippet or specific test criteria).
4. Plan Persistence
The finalized plan must be written to docs/ciel/plans/YYYY-MM-DD-<topic>-plan.md and indexed in MemPalace as a ProposedPlan node.
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 · 79 lines · 16 tokens per session scan A 2e1795e99218
make-plan is a skill published in the GitHub repository jxoesneon/Ciel (1 stars, last pushed 4d ago), licensed Apache-2.0. It adds 16 tokens to every session and 705 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…
ticket-spec
Turn a raw Linear Triage ticket into a fully specified ai:agent-ready one by exploring the codebase. Use when specifying, refining, or promoting tickets, or when asked why a ticket isn't dispatchable.
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.