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 infino-ai/code-context --skill code-contextgit clone --depth 1 https://github.com/infino-ai/code-contextWrote 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/infino-ai/code-context/code-context)<a href="https://agentmods.dev/skills/infino-ai/code-context/code-context"><img src="https://agentmods.dev/badge/skills/infino-ai/code-context/code-context/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/infino-ai/code-context/code-context"><img src="https://agentmods.dev/badge/skills/infino-ai/code-context/code-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00103 | $0.01176 |
| Opus 5.5 | $0.00041 | $0.00470 |
| Sonnet 5.5 | $0.00021 | $0.00235 |
| Haiku 4.5 | $0.00010 | $0.00118 |
Grade A, and why
code-context 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.
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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
code-context: ranked search over the repository
code-context maintains a local index of the repository (in .infino/ at the
repo root) and exposes three MCP tools. The more a question spans the repo,
the more one ranked pass beats crawling files into context.
If the tools are deferred
When the tool names appear in a deferred-tools listing but their schemas are
not loaded, load all three in ONE ToolSearch call before the first use, e.g.
query +code-context search sql reindex (or select: with the exact
listed names, comma-separated). Never load them one call at a time.
Choosing the right tool
| Situation | Use |
|---|---|
| One known identifier, literal string, or file | plain grep / file tools |
| "How does X work", "where is Y handled", concept without exact name | search |
| Counts, rankings, GROUP BY across the repo ("which files have the most code about X") | sql |
| Working tree changed a lot mid-session | reindex (usually unnecessary - see lifecycle) |
search
- Pass terms, a phrase, or a plain-language description; one pass fuses BM25 keyword matching with semantic similarity, so it works whether or not you know the exact words.
- One good search beats several narrow ones - put both the identifiers you know and the intent into a single query.
- Every hit carries
path,startLine-endLine, and the chunk content with a relevance score. Answer from the chunk content when it suffices, citing thepath:lineranges; open a file only for what the chunks don't show. - If a hit is marked
truncated, Read exactly its start-end range (offset/limit), not the whole file. k(default 10, max 50) bounds hits; raise it for survey-style questions.- Until the index's vector stage finishes, results say they are keyword-ranked; they are still real, cited hits.
sql
One read-only SELECT/WITH statement over the table
chunks(path, start_line, end_line, lang, symbol, content[, embedding]).
Search functions are callable as table-valued relations, so one query can
rank AND aggregate:
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.
- 1mo ago First seen · 108 lines · 103 tokens per session scan A 28702c9aca7c
code-context is a skill published in the GitHub repository infino-ai/code-context (31 stars, last pushed 25d ago), licensed Apache-2.0. It adds 103 tokens to every session and 1,176 once invoked, about $0.0004 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.
Other skills, from other repositories
x-ray
Deep codebase exploration using semantic search and relationship mapping. Use when you need to understand the current codebase.
ctxo-safe-edit
Use BEFORE editing, renaming, or deleting any function, class, or method, to avoid breaking dependents.
Sverklo Code Intelligence
Gives you deep codebase understanding — semantic search, blast-radius analysis, PR review, and health audits.
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…
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…
support-ticket-triage
Triage support tickets by pulling helpdesk context, searching issue trackers and knowledge bases in parallel, classifying the issue, and giving reps a recommended next action.