x-ray

x-ray is a skill for Claude Code from bartolli/codanna. It costs 25 tokens per session (1,998 once invoked), scanned A, original, Apache-2.0.

A codebase-exploration workflow that uses meaning-based search and relationship mapping to investigate an existing project. It turns a broad question into focused searches and source inspection.

In plain words
What is it for?
Finding code by concept, tracing how components relate, and inspecting the source needed to answer questions about a repository.
Why use it?
It helps locate the relevant implementation and understand connected code when file names or terminology are unfamiliar.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the codanna-toolset plugin — 2 skills shipped together

Good fit Finding code by concept, tracing how components relate, and inspecting the source needed to answer questions about a repository.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bartolli/codanna/x-ray
Install

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.

Any agent
npx skills add bartolli/codanna --skill x-ray
Clone the repo
git clone --depth 1 https://github.com/bartolli/codanna

Made for: Claude Code.

Or install codanna-toolset, the plugin that ships this one along with the rest of its 2 skills.

Wrote 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.

agentmods badge for x-ray

README.md
[![agentmods](https://agentmods.dev/badge/skills/bartolli/codanna/x-ray/github.svg)](https://agentmods.dev/skills/bartolli/codanna/x-ray)
Your own site
<a href="https://agentmods.dev/skills/bartolli/codanna/x-ray"><img src="https://agentmods.dev/badge/skills/bartolli/codanna/x-ray/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.

agentmods 80×15 button for x-ray

Your own site · 80×15
<a href="https://agentmods.dev/skills/bartolli/codanna/x-ray"><img src="https://agentmods.dev/badge/skills/bartolli/codanna/x-ray.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,998 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00025 $0.01998
Opus 5.5 $0.00010 $0.00799
Sonnet 5.5 $0.00005 $0.00400
Haiku 4.5 $0.00003 $0.00200

Measured 1mo ago against content hash 0100e7b165c2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo ago.

The scan reads SKILL.md. This mod also ships 20 executable files (graph/bundle-render.js, graph/collapse-render.js, graph/dag-render.js, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

agents/plugins/claude/codanna-toolset/skills/x-ray/SKILL.md · 172 lines

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

  1. SEARCH(OptimizedQuery)
  2. For each RESULT with SCORE > 0.6:
    • INSPECT if signature/doc is insufficient
    • TRAVERSE 1–2 RELATIONSHIPS that look load-bearing
  3. Picture incomplete → REFINE with what you learned
  4. 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

Read the full file on GitHub · 172 lines

Changes

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.

  1. 1mo ago First seen · 172 lines · 25 tokens per session scan A 0100e7b165c2

Subscribe to this mod's changes

x-ray is a skill published in the GitHub repository bartolli/codanna (754 stars, last pushed 6d 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.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.

Related

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…

bvolpato/ivygrep · 65 tokens

memtrace-first

Route code discovery, debugging, flow tracing, how-code-works questions, and pre-edit rationale checks in indexed source-code repos to Memtrace graph plus Cortex decision tools. Use first before searching/reading code, and before editing, refactoring, deleting, or re-picking an approach that may have a recorded…

syncable-dev/memtrace-public · 115 tokens

memtrace-incident-investigation

Investigate source-code bugs, incidents, regressions, production issues, and failures to root cause with Memtrace symbol search, impact, call graph, and temporal history. Use when the user asks about root cause analysis, what broke, or what changed when debugging a failure. Do not start with Grep, Glob, rg, find, or…

syncable-dev/memtrace-public · 99 tokens

memtrace-preflight

Run a one-call pre-flight check on a single existing symbol before editing it: blast radius, co-change partners, complexity, 30-day churn, and verification checklist, then check Cortex decision memory for rationale/bans when intent may matter. Use before modifying any existing function or symbol you did not just…

syncable-dev/memtrace-public · 102 tokens

memtrace-cochange

Find files that historically co-change with a target symbol or file, ranked by co-occurrence across git episodes. Use when the user asks about historical coupling, co-change, what changes with this, hidden dependencies, or what else needs to move for source code. Do not use git log, git diff, Grep, or manual file…

syncable-dev/memtrace-public · 88 tokens

memtrace-episode-replay

Replay the graph diff of one episode — a single git commit or working-tree save — to inspect what it changed: added/modified/removed symbols and edges. Use when the user asks what one commit or save changed in the graph, why code looks this way, or wants to inspect implementation attempts, reversions, past reasoning…

syncable-dev/memtrace-public · 125 tokens