Borrowing it
Nothing to install: this file belongs to sponge-b0b/Polaris. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sponge-b0b/Polaris/main/.agents/skills/codegraph/SKILL.mdgit clone --depth 1 https://github.com/sponge-b0b/PolarisWrote 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/sponge-b0b/polaris/codegraph)<a href="https://agentmods.dev/skills/sponge-b0b/polaris/codegraph"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/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/sponge-b0b/polaris/codegraph"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/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.00055 | $0.00797 |
| Opus 5.5 | $0.00022 | $0.00319 |
| Sonnet 5.5 | $0.00011 | $0.00159 |
| Haiku 4.5 | $0.00006 | $0.00080 |
Grade A, and why
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 22d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CodeGraph Analysis Skill
Objective
Expose the dynamic edge-synthesizer engine to trace implicit Python execution flows, runtime framework routing configurations, asynchronous event loops, and string-keyed callbacks that static AST tools or raw grep queries miss.
Routing Boundary
Select CodeGraph only when the material path depends on implicit or decoupled runtime dispatch. Do not select it merely because Python is changing or for ordinary symbol lookup, imports, direct call graphs, static dependencies, or diff impact; use $codebase-memory-mcp for those. Use $repowise for behavioral location and repository risk/history, $graphify for broad corpus/community exploration, and rg or direct reads for literals and non-code authority.
Context Inputs
- Authoritative Edge Registry:
.codegraph/(Driven by a native, always-on SQLite backend). - Live File Watcher: The underlying MCP background daemon runs an active background filesystem watcher. It automatically captures file saves and incrementally syncs the graph under a second—manual index rebuilds are completely unnecessary.
Guardrail Constraints
- Edge Resolution Invariant: Only trust edges that resolve completely from end to end.
- Blind-Spot Rule: If a trace yields a partial or broken path matching an interface boundary, log it explicitly as a "CodeGraph blind spot." Stop digging through files along that specific trajectory to avoid generating unnecessary file-read overhead.
- Staleness Detection (Debounce Window): If you make a rapid succession of edits, CodeGraph might display a minor staleness banner (⚠️) for a few milliseconds while the quiet window processes. If you see this banner, read the modified target file directly instead of over-relying on the graph query.
Execution Steps
When investigating runtime call paths, decoupled handlers, or asynchronous routing flows, run the CodeGraph tools based on your investigative intent:
1. Verification of System Pathing & Readiness
Before initializing dynamic code exploration, verify that the local repository background daemon is healthy and connected:
- Run:
codegraph statusto validate the state of the active tracking databases.
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.
- 22d ago Changed · +4 lines · -4 tokens per session 6d5b9a3c0ee5
- 1mo ago First seen · 54 lines · 59 tokens per session scan A cbca3b84af68
codegraph is a skill published in the GitHub repository sponge-b0b/Polaris (4 stars, last pushed today), licensed Apache-2.0. It adds 55 tokens to every session and 797 once invoked, about $0.0002 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
python-code-quality
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.
plugin-architecture-patterns
Design, implement, or diagnose Xberg plugin traits, typed registries, priority collisions, lifecycle, native extractors, and Alef-generated Python plugin bridges. Load for plugin-system work, not ordinary extractor parsing.
test-corpus
The testdocuments submodule is a bucket-fetched fixture corpus that is not committed. This skill covers readtestfixture, missing fixtures, valid A/B controls, and submodule push order. Load before running Rust tests on a fresh clone, setting up an A/B control, adding a fixture-backed test, or diagnosing…
stack-trace-python-probe
Internal helper for meta-stack-trace-investigator. Use when a Python traceback needs Python-specific root-cause checks, pytest reproducer guidance, and defensive patch targets.
idapython
IDA Pro Python scripting for reverse engineering. Use when writing IDAPython scripts, analyzing binaries, working with IDA's API for disassembly, decompilation (Hex-Rays), type systems, cross-references, functions, segments, or any IDA database manipulation. Covers ida modules (50+), idautils iterators, and common…
memory-optimization
Optimize Python code for reduced memory usage and improved memory efficiency. Use when asked to reduce memory footprint, fix memory leaks, optimize data structures for memory, handle large datasets efficiently, or diagnose memory issues. Covers object sizing, generator patterns, efficient data structures, and memory…