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 coding-standardsgit 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/coding-standards)<a href="https://agentmods.dev/skills/jxoesneon/ciel/coding-standards"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/coding-standards/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/coding-standards"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/coding-standards.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.00020 | $0.00667 |
| Opus 5 | $0.00010 | $0.00333 |
| Sonnet 5 | $0.00004 | $0.00133 |
| Haiku 4.5 | $0.00002 | $0.00067 |
Grade A, and why
coding-standards 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 6d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CIEL ADAPTATION: Coding-Standards (Engineering Baseline)
This skill provides the baseline engineering conventions applicable across CIEL projects. It establishes the "shared floor" for code quality, focusing on readability, immutability, and architectural soundness.
Integration Context
Adapted from ~/.agents/skills/coding-standards/. This skill serves as a foundational reference for the Auditor sub-agent during execution and the Verification-Loop during finality, ensuring that all code meets CIEL's definition of "high quality."
Core Principles (The Iron Laws)
- Readability First: Code is read more than written. Prefer descriptive names and self-documenting code over comments.
- KISS (Keep It Simple, Stupid): Implement the simplest solution that works. Avoid premature optimization and over-engineering.
- DRY (Don't Repeat Yourself): Extract common logic into reusable functions/components.
- YAGNI (You Aren't Gonna Need It): Do not build features speculatively.
Mandated Patterns
1. Immutability (CRITICAL)
- NEVER mutate variables directly.
- ALWAYS use the spread operator (
...) or array methods that return new instances (e.g.,map,filter).
2. Error Handling
- ALWAYS use comprehensive
try/catchblocks for asynchronous operations. - NEVER swallow errors silently. Provide user-friendly error messages and log technical details.
3. Code Smells
The Auditor sub-agent MUST reject implementations containing:
- Functions exceeding 50 lines (Long Functions).
- Logic nesting deeper than 3 levels (Deep Nesting) — use early returns.
- Unexplained "Magic Numbers" — use named constants.
Orchestration Logic
- Implementation Phase: When a sub-agent generates code, it must consult this skill to ensure naming and structural compliance.
- Review Phase: The Verification-Loop cross-references the diff against these standards to catch anti-patterns before declaring a task "READY."
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.
- 6d ago First seen · 69 lines · 20 tokens per session scan A 74403fc71a80
coding-standards is a skill published in the GitHub repository jxoesneon/Ciel (1 stars, last pushed 2d ago), licensed Apache-2.0. It adds 20 tokens to every session and 667 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-documentation
Reviews the accuracy and writing quality of documentation. Use when reviewing doc changes in a diff, checking a new or edited page, or auditing the documentation of a codebase.
review-architecture
Reviews the structural quality of code. Use when reviewing structural changes in a diff, checking a new or edited module boundary, or auditing the architecture of a codebase.
review-behaviors
Reviews the quality and coherence of behavior statements. Use when reviewing behavior changes in a diff, checking a new or edited behavior statement, or auditing the behavior statements of a codebase.
Code Quality Review
Conduct a comprehensive code quality review focused on clean code, architecture, and project standards.
code-review
Revisão holística pré-commit (estilo PR Review). Valida o diff contra as 3 memórias vivas, a spec da task e Clean Code, com pré-condição de evidência de teste. Executada pelo Tech Lead; veredito escrito em review.md.
guard
Automatiza ADRs (Architecture Decision Records) e verifica conformidade arquitetural do diff. Use para "criar ADR", "validar arquitetura" ou "checar padrões".