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 Nxtsoft/CGraph --skill cgraph-enrichgit clone --depth 1 https://github.com/Nxtsoft/CGraphWrote 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/nxtsoft/cgraph/cgraph-enrich)<a href="https://agentmods.dev/skills/nxtsoft/cgraph/cgraph-enrich"><img src="https://agentmods.dev/badge/skills/nxtsoft/cgraph/cgraph-enrich/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/nxtsoft/cgraph/cgraph-enrich"><img src="https://agentmods.dev/badge/skills/nxtsoft/cgraph/cgraph-enrich.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.00128 | $0.01443 |
| Opus 5.5 | $0.00051 | $0.00577 |
| Sonnet 5.5 | $0.00026 | $0.00289 |
| Haiku 4.5 | $0.00013 | $0.00144 |
Grade A, and why
cgraph-enrich 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 3d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cgraph-enrich
cgraph extracts code structure deterministically, but documentation, design notes, and other prose only enter the graph as host-authored semantic fragments. This skill is the loop that produces them. The native tool owns chunk planning, fragment validation, content-hash caching, and graph mutation; you (the model) own reading each chunk and authoring the fragment. No model logic lives in the binary.
The loop
Run from the project root. Repeat until the plan reports 0 input(s).
-
Plan —
cgraph enrich-plan --root . --out cgraph-outWritescgraph-out/semantic-drop/plan.json, listing only uncached or stale chunks. Each chunk hasinputs[].pathand afragmentfield — the exact filename to drop. Already-enriched files are skipped via the content-hash cache. Fragment names are offset past the fragments already in the drop dir, so the directory accumulates across passes and a new pass never overwrites an earlier one — always read the fresh plan and use the names it gives. -
Author — for each chunk in
plan.json:- Read every file in
inputs[].path. - Author ONE fragment capturing the chunk's concepts and how they relate to each other and to the code (see Fragment shape below).
- Write it atomically to
cgraph-out/semantic-drop/<chunk.fragment>— the filename from the chunk'sfragmentfield, never a name you pick yourself. Write a temp file in that directory, then rename it into place. Do not reuse or overwrite an existing fragment file.
- Read every file in
-
Merge — one of:
- Batch:
cgraph enrich-ingest --root . --out cgraph-outvalidates every dropped fragment, merges the valid ones, updates the cache, and re-exports. - Live: if a daemon is running (
graph_status), dropping the file is enough — the watcher validates and merges it into the live snapshot within ~200ms.
- Batch:
-
Verify & repeat — re-run
enrich-plan. Enriched files are now cache hits and drop out.graph_statusshowsenrichment_pendingfalling andnode_countrising. Loop until pending is 0. Malformed fragments are rejected and leave the graph unchanged (enrichment_state: failed); fix and re-drop the samechunk_<index>.json.
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.
- 3d ago Changed · +1 lines c03b01057651
- 1mo ago First seen · 106 lines · 128 tokens per session scan A d200023277d9
cgraph-enrich is a skill published in the GitHub repository Nxtsoft/CGraph (2 stars, last pushed 2d ago), licensed MIT. It adds 128 tokens to every session and 1,443 once invoked, about $0.0005 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…