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-clinpx skills add douglasmonsky/codex-usage-tracker --skill gitnexus-cligit 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.00059 | $0.01225 |
| Opus 5 | $0.00030 | $0.00613 |
| Sonnet 5 | $0.00012 | $0.00245 |
| Haiku 4.5 | $0.00006 | $0.00122 |
Grade A, and why
gitnexus-cli 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 yesterday.
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
83% identical to gitnexus-cli — 35 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitNexus CLI Commands
Commands below use node .gitnexus/run.cjs <command> — the project-local runner gitnexus analyze drops next to the index. It auto-selects an available runner at call time (global gitnexus, else pnpm dlx, else npx), so no package-manager assumption and no global install is required.
Not analyzed yet, or
node .gitnexus/run.cjsreportsCannot find module(the gitignored runner is absent — e.g. a fresh clone orgit clean)? Build only the local index withnpx gitnexus analyze --index-only .from the project root. On npm 11.x, ifnpxcrashes during install (node.target is null), install once withnpm i -g gitnexus(thengitnexus analyze --index-only .) or usepnpm --allow-build=@ladybugdb/core --allow-build=gitnexus --allow-build=tree-sitter dlx gitnexus@latest analyze --index-only .. See #1939.
Commands
analyze — Build or refresh the index
node .gitnexus/run.cjs analyze --index-only .
Run from the project root. This parses source files, builds the knowledge graph,
and writes it to .gitnexus/ without modifying repository guidance.
| Flag | Effect |
|---|---|
--force |
Force full re-index even if up to date |
--embeddings |
Enable embedding generation for semantic search (off by default) |
--drop-embeddings |
Drop existing embeddings on rebuild. By default, an analyze without --embeddings preserves them. |
--pdg |
Build the program-dependence layers used by explain and pdg_query (taint, CDG, and REACHING_DEF). |
--index-only |
Refresh only the graph; do not rewrite agent guidance or repo-local skills. |
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.
- yesterday First seen · 100 lines · 59 tokens per session scan A 0056cabd03c7
gitnexus-cli is a skill published in the GitHub repository douglasmonsky/codex-usage-tracker (193 stars, last pushed 11d ago), licensed MIT. It adds 59 tokens to every session and 1,225 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to gitnexus-cli, differing in 35 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…