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 architecture-decision-recordsgit 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/architecture-decision-records)<a href="https://agentmods.dev/skills/jxoesneon/ciel/architecture-decision-records"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/architecture-decision-records/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/architecture-decision-records"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/architecture-decision-records.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.00014 | $0.00584 |
| Opus 5 | $0.00007 | $0.00292 |
| Sonnet 5 | $0.00003 | $0.00117 |
| Haiku 4.5 | $0.00001 | $0.00058 |
Grade A, and why
architecture-decision-records 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: Architecture Decision Records (ADR)
This skill provides CIEL's framework for capturing the "Why" behind architectural choices. It ensures that every major decision is documented, reasoned, and auditable.
Integration Context
Adapted from ~/.agents/skills/architecture-decision-records/. This skill serves as the "Journal of Evolution" for CIEL, providing the historical context needed for self-improvement and future deliberations.
The ADR Format
Every ADR must follow the standardized CIEL schema:
- Context: What problem are we solving? What are the constraints?
- Decision: The specific choice being made (Present Tense).
- Alternatives: What was rejected and why?
- Consequences: What becomes easier? What becomes harder?
- Council Alignment: Record the Council of Five lens-specific votes.
Orchestration Logic
1. Decision Detection
The orchestration skill must trigger an ADR draft whenever the Council of Five reaches a significant verdict.
2. Council Persistence
Every approved ADR must be indexed in MemPalace as a high-signal "Decision" node, enabling CIEL to answer "Why did we choose X?" across sessions.
3. Lifecycle Management
Use the proposed -> accepted -> [deprecated | superseded] lifecycle. When a new ADR supersedes an old one, the Knowledge Graph in MemPalace must be updated with an invalidates relationship.
4. Verification
An ADR is "finalized" when:
- It is approved by the user.
- It is recorded in
docs/adr/. - The
index.json(or ADR README) is updated. - It is mined into MemPalace.
Original Documentation preserved at source.
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 · 74 lines · 14 tokens per session scan A 6747153190d0
architecture-decision-records is a skill published in the GitHub repository jxoesneon/Ciel (1 stars, last pushed 4d ago), licensed Apache-2.0. It adds 14 tokens to every session and 584 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.