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 agentmods add skills/jxoesneon/ciel/code_analysisnpx skills add jxoesneon/Ciel --skill code_analysisgit clone --depth 1 https://github.com/jxoesneon/CielWhat 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 | $0.00016 | $0.00301 |
| Opus 5 | $0.00008 | $0.00151 |
| Sonnet 5 | $0.00003 | $0.00060 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
code_analysis 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 2d 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
code_analysis
Read and understand code.
Operations
code.map(dir)— build a high-level map (languages, modules, entry points).code.symbol(name, path?)— definitions + references.code.deps(path)— import graph for a file.code.trace(start_symbol)— call chain.code.architecture(dir)— summarize top-level architecture.
I/O Contract
io_contract:
input: { op, path_or_symbol, "scope?" }
output: { result: structured_map }
idempotent: true
side_effects: [fs]
Strategy
Prefer existing LSPs / language-aware tools (tree-sitter, ripgrep, cargo tree, npm ls, pydeps). Falls back to regex/grep heuristics.
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.
- 2d ago First seen · 38 lines · 16 tokens per session scan A ff8c6333944e
code_analysis is a skill published in the GitHub repository jxoesneon/Ciel (1 stars, last pushed 2d ago), licensed Apache-2.0. It adds 16 tokens to every session and 301 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-08-31.
Other skills, from other repositories
build-personal-brain
Create, resume, validate, connect, or maintain a private cross-project memory for AI assistants. Use when a person asks to build a personal memory from local work folders and past assistant conversations, continue an interrupted memory audit, connect an existing memory to another local assistant, verify that the…
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-skills
Reviews Agent Skills. Use when auditing skills in a codebase, checking a new or edited SKILL.md, or verifying that a skill follows the Agent Skills spec.
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.
review-tests
Reviews test quality and coverage. Use when checking that a diff has adequate tests, checking a new or edited test, or auditing the test suite of a codebase.
testing-rate-limiting
Apply deterministic SlowAPI rate-limiter isolation for FastAPI transport tests, especially to avoid flaky HTTP 429 responses.