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 skills add Arenukvern/mcp_flutter --skill gitnexus-guidegit clone --depth 1 https://github.com/Arenukvern/mcp_flutterWrote 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/arenukvern/mcp_flutter/gitnexus-guide)<a href="https://agentmods.dev/skills/arenukvern/mcp_flutter/gitnexus-guide"><img src="https://agentmods.dev/badge/skills/arenukvern/mcp_flutter/gitnexus-guide/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.
<a href="https://agentmods.dev/skills/arenukvern/mcp_flutter/gitnexus-guide"><img src="https://agentmods.dev/badge/skills/arenukvern/mcp_flutter/gitnexus-guide.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00056 | $0.02518 |
| Opus 5.5 | $0.00022 | $0.01007 |
| Sonnet 5.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 17d 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- gitnexus-guide — 100% identical, 82 lines differ
- gitnexus-guide — 100% identical, 82 lines differ
- gitnexus-guide — 100% identical, 82 lines differ
- gitnexus-guide — 100% identical, 82 lines differ
- gitnexus-guide — 100% identical, 82 lines differ
- gitnexus-guide — 100% identical, 82 lines differ
- gitnexus-guide — 100% identical, 82 lines differ
- gitnexus-guide — 100% identical, 82 lines differ
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.
- 17d ago Changed · +74 lines 746d057790de
- 1mo ago First seen · 65 lines · 56 tokens per session scan A 40b047beeb9a
gitnexus-guide is a skill published in the GitHub repository Arenukvern/mcp_flutter (389 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 2,518 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
firebase-crashlytics
Use when implementing crash reporting, capturing fatal/non-fatal errors, recording isolate/async exceptions, customizing reports, or uploading obfuscated symbols.
flutter-errors
Use when hitting layout errors (RenderFlex overflow, unbounded constraints, RenderBox not laid out), scroll errors, or setState-during-build errors.
signals-lint
Standardized compiler diagnostics, static analysis lints, and automated IDE quick-fixes.
he-learn
Prevent verified repeated failures and preserve lasting decisions in terse ADRs. Use when failures recur, prevention needs strengthening, or accepted decisions and steering need durable capture; skip ordinary one-off fixes and routine task updates.
integrating-sentry
Integrates Sentry error tracking and performance monitoring into Flutter apps using sentryflutter. Use when setting up crash reporting in Flutter, calling SentryFlutter.init, adding SentryNavigatorObserver to GoRouter, tracing HTTP requests with sentrydio, capturing handled exceptions via Sentry.captureException…
fl-error-handling
Routes thrown errors through CoreBlocBase + CoreDelegate to StateBase's ErrorType-driven dialog/snackbar/login UI rather than a custom Failure type.