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/vkirill/agent-consult/gitnexus-guidenpx skills add VKirill/agent-consult --skill gitnexus-guidegit clone --depth 1 https://github.com/VKirill/agent-consultWrote 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/vkirill/agent-consult/gitnexus-guide)<a href="https://agentmods.dev/skills/vkirill/agent-consult/gitnexus-guide"><img src="https://agentmods.dev/badge/skills/vkirill/agent-consult/gitnexus-guide.svg" alt="Measured on agentmods" 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 | $0.00043 | $0.00747 |
| Opus 5 | $0.00022 | $0.00374 |
| Sonnet 5 | $0.00009 | $0.00149 |
| Haiku 4.5 | $0.00004 | $0.00075 |
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 4d 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
86% identical to gitnexus-guide — 8 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Usage
Loaded automatically when its description matches the active task. The body below provides the working context.
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
npx gitnexus analyzein 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 |
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) |
list_repos |
Discover indexed repos |
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.
- 4d ago First seen · 69 lines · 43 tokens per session scan A a78da3f089c1
gitnexus-guide is a skill published in the GitHub repository VKirill/agent-consult (1 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 747 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to gitnexus-guide, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
implementation_review_supervisor
Autonomous code review — supervisor delegates to engineer subagents with knowledge base.
issue_analyse_supervisor
Autonomous issue analysis — supervisor delegates to engineer subagents.
plan_review_supervisor
Autonomous plan review — supervisor delegates to engineer subagents.
issue_approve
Approve issue to transition to next workflow status.
implement-direct
Implement a small, well-defined issue directly — no planning phase, no task tracker.
issue_update
Update GitHub issue with refined content from analysis discussion.