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/r1ck29/claude-code-codegraph-harness/code-intelligencenpx skills add R1ck29/claude-code-codegraph-harness --skill code-intelligencegit clone --depth 1 https://github.com/R1ck29/claude-code-codegraph-harnessWhat 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.00026 | $0.00541 |
| Opus 5 | $0.00013 | $0.00270 |
| Sonnet 5 | $0.00005 | $0.00108 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
code-intelligence 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 today.
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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code intelligence routing
Apply this skill only when the question is structural. The configured approved code-graph MCP is a local gateway; the presence of this skill alone does not prove that the gateway or its index is usable.
Data boundary
Use only the registered local gateway. Do not register or call an upstream graph backend directly. Do not send source or graph output to another service.
Allowed graph tools
Only these five read-only gateway tools are in scope:
codegraph_statuscodegraph_searchcodegraph_neighborscodegraph_impactcodegraph_architecture
Every normal query revalidates freshness and returns it in the same response. Inspect that field; do not add a redundant codegraph_status preflight. Use codegraph_status only for diagnostics when no structural query is otherwise needed. Keep search limits and traversal depth bounded.
Routing
Use the graph only for structural tasks:
- symbol discovery
- callers and callees
- dependency paths
- neighbors and hubs
- architecture boundaries
- change-impact candidates
Use Read, Grep, LSP and relevant tests first for:
- exact control flow
- error and validation behavior
- runtime dependency injection
- reflection and generated code
- configuration-driven behavior
- final change decisions
Fail-closed fallback
If status or any result is unavailable, stale, dirty, truncated, stop using graph evidence for the task and fall back to Read, Grep, LSP. Do not ask the user to repair graph state during a coding task.
Evidence boundary
The graph is derived static-analysis data, not source-of-truth. The current source and tests are the source-of-truth. Open consequential source locations and verify relevant tests before proposing or making a change. Clearly separate graph-derived candidates from claims verified in source and tests.
What ships with it
2 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.
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.
- today First seen · 59 lines · 26 tokens per session scan A 2ad02cceaaab
code-intelligence is a skill published in the GitHub repository R1ck29/claude-code-codegraph-harness (0 stars, last pushed 9d ago), licensed Apache-2.0. It adds 26 tokens to every session and 541 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
projectatlas
Use ProjectAtlas as the atlas-first orientation layer before broad source reads, with MCP-first task startup, short-alias worktree registration and routing, safe targeted initialization, ranked navigation, exact or federated graph evidence, purpose curation, health, lint, and repository-wide token reporting.
codex-coding-plugin
Build, review, or fix ProjectAtlas plugin/runtime installer integration for Codex, Claude Code, and OpenCode, especially version convergence, stale ProjectAtlas cache repair, MCP config generation, skill artifacts, host smoke tests, and fake-host tests for ProjectAtlas releases.
research
Performs deep research on a topic via deepresearch. Simulates a multi-step research process and returns a comprehensive research result as a string.
octocode-chrome-devtools
Use when a live page needs Chrome DevTools/CDP evidence: network failures, console errors, performance, DOM/CSS actionability, screenshots/PDF, cookies/storage, click/fill/search, HAR, or auth-gated pages. Phrases like debug in Chrome, live page health, CDP snapshot, cookie bridge. Not for static crawl or bulk extract…
octocode-subagent
Use when spawning workers or offloading work: Task/subagents, specialist handoffs, A2A peers, sealed packets, coordinate/synthesize, challenge techniques (rubber-duck, interview, mimic-flow, red-team, blind review, consensus), or local Ollama one-shots to save tokens. Measuring keep/discard KPIs → octocode-graph-eval.
octocode-roast
Use when code needs a blunt evidence-backed roast or memorable critique: smell inventory, debt ranking, hot-path autopsy, savage/diff review, security or performance sins, or practical redemption paths. Phrases like roast this, brutal review, top sins, cleanup debt. Polite evidence-first PR review → octocode-research.