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/holetron-lab/godcrm/gitnexus-clinpx skills add Holetron-lab/godcrm --skill gitnexus-cligit clone --depth 1 https://github.com/Holetron-lab/godcrmWhat 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.01088 |
| Opus 5 | $0.00030 | $0.00544 |
| Sonnet 5 | $0.00012 | $0.00218 |
| Haiku 4.5 | $0.00006 | $0.00109 |
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 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
92% identical to gitnexus-cli — 1 line 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 — 86 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)? (Re)generate it withnpx gitnexus analyzefrom the project root. On npm 11.x, ifnpxcrashes during install (node.target is null), install once withnpm i -g gitnexus(thengitnexus analyze) or usepnpm --allow-build=@ladybugdb/core --allow-build=gitnexus --allow-build=tree-sitter dlx gitnexus@latest analyze. See #1939.
Commands
analyze — Build or refresh the index
node .gitnexus/run.cjs analyze
Run from the project root. This parses all source files, builds the knowledge graph, writes it to .gitnexus/, and generates CLAUDE.md / AGENTS.md context files.
| 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. |
When to run: First time in a project, after major code changes, or when gitnexus://repo/{name}/context reports the index is stale. In Claude Code, a PostToolUse hook detects staleness after git commit and git merge and notifies the agent to run analyze — the hook does not run analyze itself, to avoid blocking the agent for up to 120s and risking KuzuDB corruption on timeout.
status — Check index freshness
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 · 86 lines · 59 tokens per session scan A 6581737584d7
gitnexus-cli is a skill published in the GitHub repository Holetron-lab/godcrm (0 stars, last pushed 3d ago), licensed MIT. It adds 59 tokens to every session and 1,088 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to gitnexus-cli, differing in 1 line, and is treated as a copy.
Other skills, from other repositories
helpscout-navigator
Use when searching HelpScout tickets, customers, or organizations. Provides correct tool selection, required sequencing, and prevents common mistakes. Triggers on "search helpscout", "find tickets", "check support inbox", "helpscout conversations", "look up customer", "find organization", "customer history".
rpgmaker-mv-mcp
Use when building, editing or reasoning about an RPG Maker MV game through the RpgMakerMVUltimate MCP server (tools prefixed rpgmaker / the 13 consolidated tools: querydatabase, createdatabaseentry, generatemap, managemapevent, analyzeproject, etc.). Covers the correct workflow so maps, NPCs, chests, shops, doors…
helmdeck-hyperframes-authoring
Author render-deterministic hyperframes compositions. Use when generating HTML/CSS/JS for hyperframes.compose, hyperframes.render, or any pipeline that produces a programmatic MP4 via hyperframes — including builtin.scaffolded-narrated-video, builtin.prompt-video, builtin.prompt-narrated-video. The framework's "render…
helmdeck-debug
Audit/debug a helmdeck deployment. When a maintainer asks to "debug helmdeck", "audit the integrations", "health-check the pipelines", or "find bugs to file", run a diagnostic sweep across EVERY pipeline and capability pack — a static check of the definitions plus a live end-to-end run sweep — classify each failure by…
helmdeck
Use helmdeck's 57 capability packs (browser, web scraping, content grounding, podcast/slide/blog/video production, image generation, stock photo search, repo orientation, filesystem, git, GitHub, HTTP, vision, document OCR/parse, Python/Node execution, typed artifact store with audit-callback verification) plus four…
codecks-mcp-extend
Add a new tool/capability to this CodecksMCP server. Use this skill whenever the user wants to extend the MCP — e.g. "add support for milestones to the MCP", "I want a tool that lists sprints", "add CRUD for cards/decks/spaces/users/tags/runs/projects/reviewers/etc", "support attaching X to Y in Codecks", "expose…