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 ciel-meta-operationsgit 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/ciel-meta-operations)<a href="https://agentmods.dev/skills/jxoesneon/ciel/ciel-meta-operations"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/ciel-meta-operations/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/ciel-meta-operations"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/ciel-meta-operations.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.00022 | $0.00507 |
| Opus 5 | $0.00011 | $0.00253 |
| Sonnet 5 | $0.00004 | $0.00101 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
ciel-meta-operations 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 7d 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.
What it actually says
CIEL ADAPTATION: Meta Operations (The Orchestrator)
This skill manages the internal logic of CIEL and its interaction with the Claude API and UI state.
Claude API Standards
- Model Selection: Opus (Architecture/Research), Sonnet (Coding/Logic), Haiku (Classification/High-volume).
- Thinking Layer: Enable
thinkingfor complex math or multi-step logic tasks. - Efficiency: Use Prompt Caching for large system prompts. Use Batches API for non-time-sensitive bulk work (50% cost reduction).
Click-Path Audit (State Integrity)
- Problem: Traditional debugging misses handlers that silently undo each other.
- Protocol:
- Map State Store actions (
setsvsresets). - Trace EVERY function call in a handler in order.
- CHECK: Does a later call undo an earlier state change? (Sequential Undo).
- CHECK: Is the final state what the label promises?
- Map State Store actions (
System Configuration (ECC)
- Installation: Use the interactive installer to select skill categories (Framework, Database, Workflow).
- Level: Choose User-level (
~/.claude/) for global tools; Project-level (.claude/) for repo-specific rules.
Anti-Patterns
- Sequential Undo:
setLoading(true); resetForm();where reset sets loading to false. - Hardcoded API Keys: Passing
sk-tokens directly in code instead of env vars. - Amnesiac Description: Writing a skill description that describes "How" instead of "When."
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.
- 7d ago First seen · 52 lines · 22 tokens per session scan A 2d7c3e152638
ciel-meta-operations is a skill published in the GitHub repository jxoesneon/Ciel (1 stars, last pushed 3d ago), licensed Apache-2.0. It adds 22 tokens to every session and 507 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
triage
Triagem e causa raiz (RCA) de bugs. Use quando o usuário reportar "erro", "bug" ou "falha" para reproduzir, classificar e isolar o problema antes de qualquer correção.
perf-audit
Analisa gargalos de performance, complexidade algorítmica (Big-O) e vazamentos de memória. Use para "otimizar query", "reduzir alocação de memória" ou "auditar gargalos".
refactor
Reestruturação segura de código sem alterar o comportamento externo, para reduzir dívida técnica. Acionada pelo Architect ou Tech Lead.
refactor-cleaner
Dead code cleanup and consolidation specialist. Use PROACTIVELY for removing unused code, duplicates, and refactoring. Runs analysis tools (knip, depcheck, ts-prune) to identify dead code and safely removes it.
gitnexus-debugging
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug".
gitnexus-exploring
Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow".