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 R1ck29/claude-code-codegraph-harness --skill company-codegraphgit clone --depth 1 https://github.com/R1ck29/claude-code-codegraph-harnessWrote 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/r1ck29/claude-code-codegraph-harness/company-codegraph)<a href="https://agentmods.dev/skills/r1ck29/claude-code-codegraph-harness/company-codegraph"><img src="https://agentmods.dev/badge/skills/r1ck29/claude-code-codegraph-harness/company-codegraph/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/r1ck29/claude-code-codegraph-harness/company-codegraph"><img src="https://agentmods.dev/badge/skills/r1ck29/claude-code-codegraph-harness/company-codegraph.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00029 | $0.00556 |
| Opus 5.5 | $0.00012 | $0.00222 |
| Sonnet 5.5 | $0.00006 | $0.00111 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
company-codegraph 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Company codegraph for Codex
This file is the distributable source for the user skill installed at $HOME/.agents/skills/company-codegraph/SKILL.md. It does not modify a global or project AGENTS.md.
Apply this skill only when the question is structural. The configured MCP server is a local gateway; this skill does not register the server and does not prove that 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 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 · 60 lines · 29 tokens per session scan A 986c183ceed7
company-codegraph is a skill published in the GitHub repository R1ck29/claude-code-codegraph-harness (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 556 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-31.
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.
roam
Codebase comprehension via roam-code CLI. Use when exploring codebases, planning modifications, debugging failures, assessing PR risk, or checking architecture health. Triggers on: understanding project structure, pre-change safety checks, finding symbols/files, blast radius analysis, affected tests, health scoring…
enola
Use Enola when investigating architecture, dependencies, blast radius, cross-repository relationships, structural regressions, or what a code change did to the system.
lsp-inspect
Full code quality audit for a file, package, or directory. Supports batch mode (directory walk with --top ranking), comparison mode (--diff for branch-only issues), severity calibration by blast radius, fix suggestions, and confidence tiers. Applies a check taxonomy (dead symbols, silent failures, error wrapping…
lsp-refactor
End-to-end safe refactor workflow — blast-radius analysis, speculative preview, apply to disk, verify build, run affected tests. Inlines lsp-impact + lsp-safe-edit + lsp-verify + lsp-test-correlation into one coordinated sequence.
lsp-understand
Deep-dive exploration of unfamiliar code — given a symbol or file, builds a complete Code Map showing type info, implementations, call hierarchy (2-level depth limit), all references, and source. Broader than lsp-explore: accepts files, synthesizes multi-symbol relationships, and produces a navigable dependency map.