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-exploringnpx skills add VKirill/agent-consult --skill gitnexus-exploringgit 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-exploring)<a href="https://agentmods.dev/skills/vkirill/agent-consult/gitnexus-exploring"><img src="https://agentmods.dev/badge/skills/vkirill/agent-consult/gitnexus-exploring.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.00055 | $0.00734 |
| Opus 5 | $0.00028 | $0.00367 |
| Sonnet 5 | $0.00011 | $0.00147 |
| Haiku 4.5 | $0.00006 | $0.00073 |
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 3d 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
89% identical to gitnexus-exploring — 26 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Usage
Loaded automatically when the description matches the active task. Specifics are documented in the body below.
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. gitnexus_query({query: "<what you want to understand>"}) → Find related execution flows
4. gitnexus_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
npx gitnexus analyzein terminal.
Checklist
- [ ] READ gitnexus://repo/{name}/context
- [ ] gitnexus_query for the concept you want to understand
- [ ] Review returned processes (execution flows)
- [ ] gitnexus_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
gitnexus_query — find execution flows related to a concept:
gitnexus_query({query: "payment processing"})
→ Processes: CheckoutFlow, RefundFlow, WebhookHandler
→ Symbols grouped by flow with file locations
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.
- 3d ago First seen · 83 lines · 55 tokens per session scan A 54cc0e34ff45
gitnexus-exploring is a skill published in the GitHub repository VKirill/agent-consult (1 stars, last pushed 2mo ago), licensed MIT. It adds 55 tokens to every session and 734 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to gitnexus-exploring, differing in 26 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.