MCP-DB: Skill for Claude Code

.claude/skills/gitnexus/gitnexus-cli/SKILL.md

gitnexus-cli is a skill for Claude Code from phatngoit/MCP-DB. It costs 59 tokens per session (1,088 once invoked), scanned A, a copy of gitnexus-cli, MIT.

Command instructions for GitNexus, a tool that indexes repositories into a searchable map of code relationships. They cover analyzing, refreshing, checking, cleaning, and documenting an index.

In plain words
What is it for?
Use them to analyze a repository, refresh its index, inspect index status, clean generated data, or create a project wiki.
Why use it?
They make repository indexing repeatable and explain what to do when the index is missing or out of date.

Skill for Claude Code

Written for Claude Code: PostToolUse hook event. Also seen: mentions CLAUDE.md; mentions Claude Code; mentions AGENTS.md.

This is phatngoit/MCP-DB's own configuration. It tells Claude Code how to work on MCP-DB itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything MCP-DB configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node .gitnexus/run.cjs analyze.

Reuse

Borrowing it

Nothing to install: this file belongs to phatngoit/MCP-DB. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/phatngoit/MCP-DB/master/.claude/skills/gitnexus/gitnexus-cli/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/phatngoit/MCP-DB

Made for: Claude Code.

Wrote 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.

agentmods badge for gitnexus-cli

README.md
[![agentmods](https://agentmods.dev/badge/skills/phatngoit/mcp-db/gitnexus-cli/github.svg)](https://agentmods.dev/skills/phatngoit/mcp-db/gitnexus-cli)
Your own site
<a href="https://agentmods.dev/skills/phatngoit/mcp-db/gitnexus-cli"><img src="https://agentmods.dev/badge/skills/phatngoit/mcp-db/gitnexus-cli/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.

agentmods 80×15 button for gitnexus-cli

Your own site · 80×15
<a href="https://agentmods.dev/skills/phatngoit/mcp-db/gitnexus-cli"><img src="https://agentmods.dev/badge/skills/phatngoit/mcp-db/gitnexus-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,088 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 92% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00059 $0.01088
Opus 5.5 $0.00024 $0.00435
Sonnet 5.5 $0.00012 $0.00218
Haiku 4.5 $0.00006 $0.00109

Measured 1mo ago against content hash 6581737584d7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

Origin

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.

.claude/skills/gitnexus/gitnexus-cli/SKILL.md · 86 lines

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.cjs reports Cannot find module (the gitignored runner is absent — e.g. a fresh clone or git clean)? (Re)generate it with npx gitnexus analyze from the project root. On npm 11.x, if npx crashes during install (node.target is null), install once with npm i -g gitnexus (then gitnexus analyze) or use pnpm --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

Read the full file on GitHub · 86 lines

Changes

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.

  1. 1mo ago First seen · 86 lines · 59 tokens per session scan A 6581737584d7

Subscribe to this mod's changes

gitnexus-cli is a skill published in the GitHub repository phatngoit/MCP-DB (1 stars, last pushed 2mo ago), licensed MIT. It adds 59 tokens to every session and 1,088 once invoked, about $0.0002 per session on Opus 5.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.

Related

Other skills, from other repositories

autoreview

Structured code review through the shared OpenClaw agent-skills installation.

openclaw/clawhub · 17 tokens

omh-code-review

This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 48 tokens

revdiff-plan

Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…

umputun/revdiff · 84 tokens

explore-unknowns

Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…

dzhng/skills · 162 tokens

asplos-writing-style

Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…

brycewang-stanford/Awesome-Journal-Skills · 65 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens