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 systematic-debugginggit 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/systematic-debugging)<a href="https://agentmods.dev/skills/jxoesneon/ciel/systematic-debugging"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/systematic-debugging.svg" alt="Measured on agentmods" 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.00019 | $0.00676 |
| Opus 5 | $0.00010 | $0.00338 |
| Sonnet 5 | $0.00004 | $0.00135 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
systematic-debugging 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 3d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CIEL ADAPTATION: Systematic Debugging
This skill enforces CIEL's diagnostic rigor: NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST.
Integration Context
Adapted from ~/.agents/skills/systematic-debugging/. This is a critical safety and quality mandate for all CIEL-orchestrated troubleshooting.
The Iron Law
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST.
If you propose a fix without a confirmed root cause: STOP. Return to Phase 1.
The Four Phases
Phase 1: Root Cause Investigation
- Evidence Gathering: Read error messages, traces, and logs completely.
- Reproduction: Create a consistent, minimal reproduction of the failure.
- Trace Back: Follow the data flow backward from the symptom to the source.
Phase 2: Pattern Analysis
- Differential Analysis: Compare the failing code against similar working examples.
- Context Mapping: Identify all dependencies, configurations, and environment variables involved.
Phase 3: Hypothesis & Minimal Testing
- Single Variable: Form a specific hypothesis and test it with the smallest possible change.
- Verification: Confirm if the minimal change proves the hypothesis before implementing a full fix.
Phase 4: Implementation (via TDD)
- Failing Test: Create an automated test that reproduces the bug (Red).
- Root Cause Fix: Address the source, not the symptom (Green).
- Architectural Gate: If 3+ fixes fail, STOP and trigger a Council Review of the architecture.
Orchestration Logic
1. Triage
The orchestration skill must ensure Phase 1 is complete before any sub-task for "fixing" is dispatched.
2. High-Risk Diagnostics
For multi-component failures, the Council of Five (specifically Safety and Efficiency) will review the diagnostic plan to ensure proper instrumentation.
3. Verification
A bug is "resolved" only when:
- The root cause is identified and addressed.
- A regression test is added to the permanent test suite.
- The Council of Five (Coherence/Safety) verifies the fix aligns with system invariants.
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.
- 3d ago First seen · 89 lines · 19 tokens per session scan A bc60cc134c9c
systematic-debugging is a skill published in the GitHub repository jxoesneon/Ciel (1 stars, last pushed 6d ago), licensed Apache-2.0. It adds 19 tokens to every session and 676 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
triage
Triagem e causa raiz (RCA) de bugs. Use quando o usuário reportar "erro", "bug" ou "falha" para reproduzir, classificar e isolar o problema antes de qualquer correção.
perf-audit
Analisa gargalos de performance, complexidade algorítmica (Big-O) e vazamentos de memória. Use para "otimizar query", "reduzir alocação de memória" ou "auditar gargalos".
refactor
Reestruturação segura de código sem alterar o comportamento externo, para reduzir dívida técnica. Acionada pelo Architect ou Tech Lead.
refactor-cleaner
Dead code cleanup and consolidation specialist. Use PROACTIVELY for removing unused code, duplicates, and refactoring. Runs analysis tools (knip, depcheck, ts-prune) to identify dead code and safely removes it.
gitnexus-debugging
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug".
gitnexus-exploring
Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow".