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/ucsandman/dashclaw/gitnexus-guidenpx skills add ucsandman/DashClaw --skill gitnexus-guidegit clone --depth 1 https://github.com/ucsandman/DashClawWhat 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.00056 | $0.02518 |
| Opus 5 | $0.00028 | $0.01259 |
| Sonnet 5 | $0.00011 | $0.00504 |
| Haiku 4.5 | $0.00006 | $0.00252 |
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 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
100% identical to gitnexus-guide — 0 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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
node .gitnexus/run.cjs 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 |
trace |
Shortest path between two symbols — "how does A reach B?" in one call |
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) |
explain |
Persisted taint findings — source→sink data flows (needs analyze --pdg) |
pdg_query |
Control/data dependence — what gates X (CDG) / where Y flows (REACHING_DEF); needs analyze --pdg |
check |
Check graph invariants such as circular imports |
route_map |
API route map — which components/hooks fetch which endpoints, and the handler files that serve them |
shape_check |
Response-shape drift — keys each route returns vs keys its consumers access (flags MISMATCH) |
api_impact |
Pre-change report for an API route — consumers, middleware, shape mismatches, risk level |
tool_map |
MCP/RPC tool definitions and the files that handle them |
group_list |
List configured multi-repo groups, or one group's config |
group_sync |
Rebuild a group's Contract Registry (cross-repo HTTP contract links); run after group.yaml changes or member re-index |
list_repos |
Discover indexed repos (paginated — limit/offset) |
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 · 139 lines · 56 tokens per session scan A 746d057790de
gitnexus-guide is a skill published in the GitHub repository ucsandman/DashClaw (296 stars, last pushed 4d ago), licensed MIT. It adds 56 tokens to every session and 2,518 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to gitnexus-guide, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
optimizer
Analyzes and automatically optimizes existing agents by improving system prompts and tool configuration.
text2agent
Creates new agents from user requirements by generating Python implementation and mcpconfig.
tiktok_download
Single-file TikTok/Douyin video download and traffic metrics via TikHub API using only httpx; optional persisted raw API JSON plus a stdlib post-processor emitting CSV and simplified JSON. Supports one URL or concurrent batch (max 10 workers). No dependency on any project codebase.
app_evaluator
A professional skill for App Evaluation (evaluating app's performance with score) and App Improvement (giving professional suggestions for improving the app's performance).
last_7_days_news
Search and summarize the latest 7 days of AI news and X discussions using public sources plus browser-based X collection. Use for recent AI news, trends, X discussions, industry briefs, and summaries organized into hot topics, viewpoints, and opportunity areas.
self_evolve
Use for framework-gated self-evolve workflows in AWorld: evolve skills, create trajectory-backed proposals, inspect self-evolve run artifacts, run aworld-cli optimize, or prepare verified apply decisions through aworld.selfevolve gates.