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 rfc-and-unit-orchestrationgit 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/rfc-and-unit-orchestration)<a href="https://agentmods.dev/skills/jxoesneon/ciel/rfc-and-unit-orchestration"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/rfc-and-unit-orchestration/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/rfc-and-unit-orchestration"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/rfc-and-unit-orchestration.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.00023 | $0.00491 |
| Opus 5 | $0.00012 | $0.00246 |
| Sonnet 5 | $0.00005 | $0.00098 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
rfc-and-unit-orchestration 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 9d 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: RFC & Unit Orchestration (The Structure Layer)
This skill formalizes the decomposition of large features into independently verifiable work units. it prioritizes quality gates and merge safety.
The RFC Pipeline
- Intake: Map high-level intent to a formal Request for Comments (RFC).
- DAG Decomposition: Split the RFC into a Directed Acyclic Graph (DAG) of work units.
- Unit Assignment: Assign units based on complexity tiers (1: Isolated, 2: Multi-file, 3: Schema/Security).
- Merge Queue: Manage the sequential integration of units. Re-run integration tests after EVERY merge.
Work Unit Specification
Every unit MUST include:
idanddepends_on.scope: Exact files or functions.acceptance_tests: Minimum proving steps.rollback_plan: How to undo the change if integration fails.
Implementation Workflow
- Research: iterative context retrieval for the unit.
- Implementation: TDD-based implementation.
- Review: Mandatory code-review turn before merge-readiness.
- Integration: Rebase and resolve conflicts on the main feature branch.
Anti-Patterns
- Zombie Dependencies: Proceeding with a unit when its required predecessor failed.
- Merge-and-Forget: Integrating a unit without re-running the full integration test suite.
- The Giant Unit: Defining a single unit that touches > 5 files across different domains.
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.
- 9d ago First seen · 55 lines · 23 tokens per session scan A 5c2229e25c08
rfc-and-unit-orchestration is a skill published in the GitHub repository jxoesneon/Ciel (1 stars, last pushed 5d ago), licensed Apache-2.0. It adds 23 tokens to every session and 491 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
review-tests
Reviews test quality and coverage. Use when checking that a diff has adequate tests, checking a new or edited test, or auditing the test suite of a codebase.
testing-rate-limiting
Apply deterministic SlowAPI rate-limiter isolation for FastAPI transport tests, especially to avoid flaky HTTP 429 responses.
fluent
Operate the fluent workflow to build software autonomously over extended periods. Interactive stages (brief, behaviors, approach, plan) run with the user. Autonomous execution loops writer → tester → parallel reviewers, then runs the Learner after a passing review round. Only a successful Learner run produces a ready…
test-scaffold
Gera estrutura completa de testes automatizados (unitários, integração e edge cases) com base no código existente. Use para "escrever testes para este arquivo", "aumentar cobertura" ou "criar mocks".
e2e-runner
End-to-end testing specialist using Playwright. Use PROACTIVELY for generating, maintaining, and running E2E tests. Manages test journeys, quarantines flaky tests, uploads artifacts (screenshots, videos, traces), and ensures critical user flows work.
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.