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 kouroshez/coding-os --skill graph-explorergit clone --depth 1 https://github.com/kouroshez/coding-osWrote 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/kouroshez/coding-os/graph-explorer)<a href="https://agentmods.dev/skills/kouroshez/coding-os/graph-explorer"><img src="https://agentmods.dev/badge/skills/kouroshez/coding-os/graph-explorer/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/kouroshez/coding-os/graph-explorer"><img src="https://agentmods.dev/badge/skills/kouroshez/coding-os/graph-explorer.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.00068 | $0.03348 |
| Opus 5.5 | $0.00027 | $0.01339 |
| Sonnet 5.5 | $0.00014 | $0.00670 |
| Haiku 4.5 | $0.00007 | $0.00335 |
Grade A, and why
graph-explorer 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 10d 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
graph-explorer
Purpose: Load the graph_os toolset (cos_graph_* MCP tools) and
use it deliberately before any non-trivial code edit. The graph is the
third retrieval layer (CLAUDE.md Three-Layer Retrieval) — use it when
tree-grep or past-memory searches return noise.
Read when: Editing src/core/** or src/cli/**, producing a rename plan,
auditing API/MCP contracts, answering "what depends on X".
Skip when: You already know the blast radius, or the change is a self-contained one-file edit with no callers.
Decision ladder
- Need to know "what calls this?" →
cos_graph_references(uid). - Need surrounding context before editing? →
cos_graph_context(uid_or_name, depth=1)(Implementer pre-impl step). - Planning a refactor? →
cos_graph_impact(uid, depth=3)(Analyst dependency map) groups edges by risk tier. - Renaming a symbol? →
cos_graph_rename_plan(uid, new_name)before anyEdit— returns call-sites, doc refs, tests, string literals. - API / contract audit? →
cos_graph_contracts(kinds=["http","mcp"])(Documenter + Deployer). - Tracing a fault? →
cos_graph_trace(entry_uid)(Debugger fault isolation step). - "Is anything similar?" →
cos_graph_similar(uid, top_k=5). - Shortest dependency path? →
cos_graph_path(source, target). - Need a diagram? →
cos_graph_export(format="mermaid", root_uid=...). - Pre-commit self-review? →
cos_graph_detect_changes(files=[...])— call BEFOREmake verify; it also lists names the touched files use but never define or import. - Copy-pasted code? →
cos_graph_duplicates(scope="src/", clone_type="exact"|"renamed")— clone groups of ≥50 tokens and identical files; tests and generated files stay out unlessinclude_tests=True. - Forgotten import / undefined name? →
cos_graph_undefined(scope=...)— names used but never defined or imported (Python, TS/JS, Go) and imports of a name the module does not export. - How many files use a library? →
cos_graph_references(uid)oncode:module:npm:react,code:module:fastapiorcode:external:github.com/gofiber/fiber/v2—data.source_filescounts each importing file once, sub-paths included, even when the rows are trimmed.
What ships with it
1 file 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.
- 10d ago Changed · +11 lines 6b34318bd739
- 1mo ago First seen · 226 lines · 68 tokens per session scan A 442e7076b67a
graph-explorer is a skill published in the GitHub repository kouroshez/coding-os (6 stars, last pushed 5d ago), licensed Apache-2.0. It adds 68 tokens to every session and 3,348 once invoked, about $0.0003 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
potpie-cli
Use when the task is centered on running, explaining, configuring, or troubleshooting the potpie command: doctor, login, pot management, source registration, resolve/search/record, graph workbench reads/writes, resource (document payload) commands, and pot scope behavior.
potpie-debug-memory
Use while debugging or troubleshooting failures, flaky tests, incidents, production alerts, CI failures, local dev setup issues, repeated bugs, prior fixes, failed attempts, and verification history.
analyze-type-infer
A compiler analysis step that infers a symbol's type from its assignments. A type describes what kind of value something holds, such as a number, text, or Boolean value.
check-name-real
A name checker that verifies every required symbol has been declared. A symbol is a named program entity such as a variable or function.
compiler-0355bffb
A virtual-machine debugging skill for executing one instruction at a time. A virtual machine is a program that runs a compact instruction format instead of native machine code.
compiler-2f8c8f39
A call-graph skill that maps which functions call which other functions. A call graph is a network whose nodes are functions and whose links represent calls.