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/bartolli/codanna/x-raynpx skills add bartolli/codanna --skill x-raygit clone --depth 1 https://github.com/bartolli/codannaWhat 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.00025 | $0.01998 |
| Opus 5 | $0.00013 | $0.00999 |
| Sonnet 5 | $0.00005 | $0.00400 |
| Haiku 4.5 | $0.00003 | $0.00200 |
Grade A, and why
x-ray 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reframe
LITERAL: "$ARGUMENTS"
Definitions
- LITERAL — what the user typed
- INTENT — what they mean, given SESSION_CONTEXT
- SESSION_CONTEXT — recent work; held by you, not by the index
- BRIDGE — your job: LITERAL + SESSION_CONTEXT → INTENT → query
Rules
- Search INTENT, not LITERAL.
- Context disambiguates → NARROW.
- Context insufficient → BROAD. Vague beats confidently-wrong-narrow.
Transforms (LITERAL → INTENT)
- VAGUE → specify ("that parsing thing" → "language parser implementation")
- QUESTION → keywords ("how does parsing work?" → "parsing implementation process")
- CONVERSATIONAL → technical ("stuff that handles languages" → "language handler processor")
- BROAD → contextualize ("errors" → "error handling exception management")
- CONTEXTUAL → reconstruct ("the logging" → "prompt eval logging", when SESSION_CONTEXT = prompt eval work)
OptimizedQuery: {written against INTENT}
Loop
Definitions
-
SEARCH —
codanna mcp semantic_search_with_context query:"<q>" limit:5 -
INSPECT — read source at a LOCATION (Read tool or
sed -n 'A,Bp' file) -
TRAVERSE —
codanna retrieve describe <name|symbol_id:N>on a RELATIONSHIP -
REFINE — return to SEARCH with a new OptimizedQuery
-
RESULT — one hit from SEARCH; carries SCORE, signature, doc, LOCATION, RELATIONSHIPS
-
SCORE — relevance ∈ [0,1]; focus on SCORE > 0.6
-
LOCATION —
file_path:start_line-end_line -
RELATIONSHIPS — calls, called_by, implements, defines
Default flow
- SEARCH(OptimizedQuery)
- For each RESULT with SCORE > 0.6:
- INSPECT if signature/doc is insufficient
- TRAVERSE 1–2 RELATIONSHIPS that look load-bearing
- Picture incomplete → REFINE with what you learned
- INTENT answered → stop
INSPECT mechanics
LOCATION src/io/exit_code.rs:108-120 →
- Read tool:
file_path=<env.cwd>/src/io/exit_code.rs, offset=108, limit=13 - limit formula:
end_line - start_line + 1 - sed (Unix only):
sed -n '108,120p' src/io/exit_code.rs
What ships with it
24 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- graph-view.html 57 KB
- graph/bundle-render.js 11 KB runs code
- graph/collapse-render.js 10 KB runs code
- graph/dag-render.js 15 KB runs code
- graph/details.js 2.9 KB runs code
- graph/dump.js 2.4 KB runs code
- graph/hierarchy.js 4.6 KB runs code
- graph/logo-cn.min.svg 18 KB
- graph/logo-cn.png 3.8 KB
- graph/logo-cn.svg 48 KB
- graph/publish.js 2.2 KB runs code
- graph/qualify.js 3.0 KB runs code
- graph/render.js 34 KB runs code
- graph/server.js 1.2 KB runs code
- graph/theme.js 22 KB runs code
- graph/tokens.mjs 7.6 KB runs code
- graph/tree-render.js 11 KB runs code
- graph/vendor/3d-force-graph.min.js 1211 KB runs code
- graph/vendor/d3.min.js 273 KB runs code
- graph/vendor/three-bundle.min.js 709 KB runs code
- visualize-bundle.js 4.2 KB runs code
- visualize-dump.js 12 KB runs code
- visualize-graph.js 8.2 KB runs code
- visualize-tree.js 4.4 KB runs code
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 · 172 lines · 25 tokens per session scan A 0100e7b165c2
x-ray is a skill published in the GitHub repository bartolli/codanna (729 stars, last pushed 4d ago), licensed Apache-2.0. It adds 25 tokens to every session and 1,998 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-30.
Other skills, from other repositories
use-ivygrep
Gather focused local repository context with ivygrep before implementing, debugging, reviewing, or explaining code. Use for coding tasks involving unfamiliar paths, branch changes, stack traces, architectural relationships, callers, dependents, tests, configuration, or documentation. Prefer one bounded context pack…
codemeridian-refactor
Plan safer refactors with CodeMeridian by checking graph freshness, exact symbols, impact, tests, duplication, and architecture risk before editing.
codemeridian-test-planning
Plan focused tests with CodeMeridian by finding relevant test shields, coverage gaps, impacted behavior, and the smallest useful test set before implementation.
human-cognitive-seed
Preserve and strengthen the user's independent reasoning during design, strategy, learning, interpretation, hypothesis work, and consequential decisions, and preserve justified durable context with explicit provenance when supported. Use when a task benefits from human-led judgment, model-building, productive…
codemeridian-context
Gather minimal, graph-grounded CodeMeridian context before implementation, refactoring, deletion, debugging, or test planning.
codemeridian-frontend
Route frontend HTML/CSS/SCSS work through CodeMeridian's generic frontend-aware tools first, then use cascade and style-duplicate analysis only when the question is truly frontend-specific.