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-quality-and-verificationgit 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-quality-and-verification)<a href="https://agentmods.dev/skills/jxoesneon/ciel/ciel-quality-and-verification"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/ciel-quality-and-verification/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-quality-and-verification"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/ciel-quality-and-verification.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.00025 | $0.00546 |
| Opus 5 | $0.00013 | $0.00273 |
| Sonnet 5 | $0.00005 | $0.00109 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
ciel-quality-and-verification 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: Quality & Verification (The Integrity Layer)
This skill formalizes the "Evidence before Claims" mandate. it prioritizes fresh verification and disciplined implementation loops.
The Iron Law (Hard Gate)
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE. If you haven't run the verification command in the CURRENT message, you cannot claim it passes.
TDD implementation loop
- RED: Write a failing test that reproduces the bug or exercises the new feature.
- GREEN: Apply the minimal implementation required to pass the test.
- REFACTOR: Improve code quality while maintaining GREEN state.
- Coverage: Mandate 80% line coverage for all production logic.
Write-Time Enforcement (Plankton)
- Silent Phase: Run formatters (Ruff/Biome) on every file edit.
- Delegation Phase: Route complex violations to specific model tiers (Haiku for style, Sonnet for logic, Opus for types).
- Enforcement: Block legacy package managers (pip/npm) in favor of modern runtimes (uv/bun).
Terminal Ops (Evidence-First)
- Workflow: surface -> Evidence -> Action -> Status.
- Integrity: Distinguish between "changed locally" and "verified locally."
- Verification: Name the specific command or test that proves the fix.
Anti-Patterns
- The "Should" Trap: Claiming code is correct because it "should work" or "looks right."
- Amnesiac Regression: Passing a test once and then moving on without verifying the RED-GREEN cycle.
- Linter-Passing ≠ Compiler-Passing: Claiming success because the linter is clean while the build is broken.
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 · 56 lines · 25 tokens per session scan A eb1a38b159b6
ciel-quality-and-verification is a skill published in the GitHub repository jxoesneon/Ciel (1 stars, last pushed 3d ago), licensed Apache-2.0. It adds 25 tokens to every session and 546 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
mutation-testing
Use when adding or reviewing a gate, guard rule, CI grep, or test assertion in this plugin's own scripts — and whenever a suite is green and you need to know whether that means anything. Runs scripts/mutate.sh, which breaks the code on purpose and reports which assertions failed to notice. Triggers from code-reviewer…
aidex-bugfix
Use when fixing a bug, resolving a reported issue, or when something is broken and needs a test-driven fix — investigate root cause, write a failing regression test (RED), implement the minimum fix, confirm the test passes (GREEN), then commit test and fix together. Fires on "fix this bug", "this is broken", "it's not…
workflow-test-fix
Unified test-fix pipeline combining test generation (session, context, analysis, task gen) with iterative test-cycle execution (adaptive strategy, progressive testing, CLI fallback). Triggers on "workflow-test-fix", "test fix workflow".
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.
tdd-guide
Test-Driven Development specialist enforcing write-tests-first methodology. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage.
build-test
Run the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.