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 documentationgit 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/documentation)<a href="https://agentmods.dev/skills/jxoesneon/ciel/documentation"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/documentation/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/documentation"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/documentation.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.00283 |
| Opus 5.5 | $0.00006 | $0.00113 |
| Sonnet 5.5 | $0.00003 | $0.00057 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
documentation 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 1mo 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
documentation
Generate and maintain project documentation.
Operations
doc.readme(project)— generate/update README.doc.api(source_path, format)— generate API docs from source (TSDoc, rustdoc, Sphinx, etc.).doc.changelog(since_ref?, style=keep-a-changelog).doc.inline(file, policy)— add/update docstrings matching project style.
I/O Contract
io_contract:
input: { op, target, "format?", "policy?" }
output: { files_written: [paths], diff }
idempotent: partial
side_effects: [fs]
Style
Respects configuration/local/rules.config.md.documentation.* and detected conventions.
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.
- 1mo ago First seen · 37 lines · 14 tokens per session scan A 97be6eaac41d
documentation is a skill published in the GitHub repository jxoesneon/Ciel (1 stars, last pushed 2d ago), licensed Apache-2.0. It adds 14 tokens to every session and 283 once invoked, about $0.0001 per session on Opus 5.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-08-31.
Other skills, from other repositories
Code Quality Review
Conduct a comprehensive code quality review focused on clean code, architecture, and project standards.
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…
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.
expert-redteam-review
Use when a user asks to evaluate a complex, high-impact, ambiguous, cross-functional, or hard-to-reverse decision; mentions expert panel, red team, adversarial review, rebuttal, judge, arbitration, risk review, challenge assumptions, poke holes, or wants stronger decision quality than a normal review.
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, em paralelo ao QA/Security (fan-out); a evidência de teste é exigida no join. Executada pelo Tech Lead; veredito escrito em review.md.