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 agentmods add skills/douglasmonsky/codex-usage-tracker/gitnexus-exploringnpx skills add douglasmonsky/codex-usage-tracker --skill gitnexus-exploringgit clone --depth 1 https://github.com/douglasmonsky/codex-usage-trackerWhat 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 | $0.00055 | $0.00690 |
| Opus 5 | $0.00028 | $0.00345 |
| Sonnet 5 | $0.00011 | $0.00138 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
gitnexus-exploring 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 2d 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
94% identical to gitnexus-exploring — 14 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exploring Codebases with GitNexus
When to Use
- "How does authentication work?"
- "What's the project structure?"
- "Show me the main components"
- "Where is the database logic?"
- Understanding code you haven't seen before
Workflow
1. READ gitnexus://repos → Discover indexed repos
2. READ gitnexus://repo/{name}/context → Codebase overview, check staleness
3. query({search_query: "<what you want to understand>"}) → Find related execution flows
4. context({name: "<symbol>"}) → Deep dive on specific symbol
5. READ gitnexus://repo/{name}/process/{name} → Trace full execution flow
If step 2 says "Index is stale" → run
gitnexus analyze --index-only .in terminal.
Checklist
- [ ] READ gitnexus://repo/{name}/context
- [ ] query for the concept you want to understand
- [ ] Review returned processes (execution flows)
- [ ] context on key symbols for callers/callees
- [ ] READ process resource for full execution traces
- [ ] Read source files for implementation details
Resources
| Resource | What you get |
|---|---|
gitnexus://repo/{name}/context |
Stats, staleness warning (~150 tokens) |
gitnexus://repo/{name}/clusters |
All functional areas with cohesion scores (~300 tokens) |
gitnexus://repo/{name}/cluster/{name} |
Area members with file paths (~500 tokens) |
gitnexus://repo/{name}/process/{name} |
Step-by-step execution trace (~200 tokens) |
Tools
query — find execution flows related to a concept:
query({search_query: "payment processing"})
→ Processes: CheckoutFlow, RefundFlow, WebhookHandler
→ Symbols grouped by flow with file locations
context — 360-degree view of a symbol:
context({name: "validateUser"})
→ Incoming calls: loginHandler, apiMiddleware
→ Outgoing calls: checkToken, getUserById
→ Processes: LoginFlow (step 2/5), TokenRefresh (step 1/3)
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.
- 2d ago First seen · 79 lines · 55 tokens per session scan A 077b34e0b1a9
gitnexus-exploring is a skill published in the GitHub repository douglasmonsky/codex-usage-tracker (193 stars, last pushed 12d ago), licensed MIT. It adds 55 tokens to every session and 690 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to gitnexus-exploring, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
cost-aware-development
先按风险选择最低可胜任能力，再决定需要多少流程和角色。简单任务保持简单；成本优化不得绕过真实风险、安全边界或完成证据。.
disposable-prototype
当实现前可用最小可运行实验回答具体技术或交互未知时使用；产物默认不可发布，且这是轻量叶子能力，不负责任务编排。.
domain-context
当开发任务需要澄清领域术语、业务不变量、CONTEXT.md 或 ADR 约束时使用；这是轻量叶子能力，不负责任务编排。.
module-design
当用户要求改善模块边界、降低耦合、缩小变更面或评估代码结构时使用；这是轻量叶子能力，不负责任务编排。.
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.
final-release-review
Perform pre-release planning or a final release-candidate review for openai-agents-python by comparing the target with the previous remote tag, determining the minimum compatible release type, auditing regressions and contract changes, reviewing open documentation PR coverage, drafting minor-release Key Changes, and…