Borrowing it
Nothing to install: this file belongs to douglasmonsky/codex-usage-tracker. 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/douglasmonsky/codex-usage-tracker/main/.claude/skills/gitnexus/gitnexus-guide/SKILL.mdgit clone --depth 1 https://github.com/douglasmonsky/codex-usage-trackerWrote 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/douglasmonsky/codex-usage-tracker/gitnexus-guide)<a href="https://agentmods.dev/skills/douglasmonsky/codex-usage-tracker/gitnexus-guide"><img src="https://agentmods.dev/badge/skills/douglasmonsky/codex-usage-tracker/gitnexus-guide/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/douglasmonsky/codex-usage-tracker/gitnexus-guide"><img src="https://agentmods.dev/badge/skills/douglasmonsky/codex-usage-tracker/gitnexus-guide.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.00056 | $0.02544 |
| Opus 5.5 | $0.00022 | $0.01018 |
| Sonnet 5.5 | $0.00011 | $0.00509 |
| Haiku 4.5 | $0.00006 | $0.00254 |
Grade A, and why
gitnexus-guide 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 2mo 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.
This is a copy
97% identical to gitnexus-guide — 70 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitNexus Guide
Quick reference for all GitNexus MCP tools, resources, and the knowledge graph schema.
Always Start Here
For any task involving code understanding, debugging, impact analysis, or refactoring:
- Read
gitnexus://repo/{name}/context— codebase overview + check index freshness - Match your task to a skill below and read that skill file
- Follow the skill's workflow and checklist
If step 1 warns the index is stale, run
gitnexus analyze --index-only .in the terminal first.
Skills
| Task | Skill to read |
|---|---|
| Understand architecture / "How does X work?" | gitnexus-exploring |
| Blast radius / "What breaks if I change X?" | gitnexus-impact-analysis |
| Trace bugs / "Why is X failing?" | gitnexus-debugging |
| Rename / extract / split / refactor | gitnexus-refactoring |
| Tools, resources, schema reference | gitnexus-guide (this file) |
| Index, status, clean, wiki CLI commands | gitnexus-cli |
Tools Reference
| Tool | What it gives you |
|---|---|
query |
Process-grouped code intelligence — execution flows related to a concept |
context |
360-degree symbol view — categorized refs, processes it participates in |
impact |
Symbol blast radius — what breaks at depth 1/2/3 with confidence |
trace |
Shortest path between two symbols — "how does A reach B?" in one call |
detect_changes |
Git-diff impact — what do your current changes affect |
rename |
Multi-file coordinated rename with confidence-tagged edits |
cypher |
Raw graph queries (read gitnexus://repo/{name}/schema first) |
explain |
Persisted taint findings — source→sink data flows (needs analyze --pdg) |
pdg_query |
Control/data dependence — what gates X (CDG) / where Y flows (REACHING_DEF); needs analyze --pdg |
check |
Check graph invariants such as circular imports |
route_map |
API route map — which components/hooks fetch which endpoints, and the handler files that serve them |
shape_check |
Response-shape drift — keys each route returns vs keys its consumers access (flags MISMATCH) |
api_impact |
Pre-change report for an API route — consumers, middleware, shape mismatches, risk level |
tool_map |
MCP/RPC tool definitions and the files that handle them |
group_list |
List configured multi-repo groups, or one group's config |
group_sync |
Rebuild a group's Contract Registry (cross-repo HTTP contract links); run after group.yaml changes or member re-index |
list_repos |
Discover indexed repos (paginated — limit/offset) |
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.
- 2mo ago First seen · 155 lines · 56 tokens per session scan A ed4ead75bf74
gitnexus-guide is a skill published in the GitHub repository douglasmonsky/codex-usage-tracker (196 stars, last pushed 15d ago), licensed MIT. It adds 56 tokens to every session and 2,544 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to gitnexus-guide, differing in 70 lines, and is treated as a copy.
Other skills, from other repositories
cost-aware-development
Guidance for choosing the smallest suitable development process based on a task's risk and complexity.
disposable-prototype
A small, isolated experiment used to answer a specific technical or interaction question before full implementation. Its code is temporary by default and is not treated as a publishable feature.
domain-context
A lightweight guide for finding and applying a project's domain terms, business rules, recorded decisions, and constraints. It can read files such as CONTEXT.md and architecture decision records when they exist.
module-design
A lightweight method for improving how code is divided into modules, where modules are parts of a program with defined responsibilities.
codex-plugin-discovery
Use when a user asks what Codex plugins are available or can be used, wants plugin recommendations for a task, asks to find/search/discover installable plugins, asks about the plugin marketplace, or asks whether a plugin can help with a task.
playwright
Use when the task requires capturing or automating a real browser from the terminal.