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/alexei-led/architect/tools-gitnexusnpx skills add alexei-led/architect --skill tools-gitnexusgit clone --depth 1 https://github.com/alexei-led/architectWrote 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/alexei-led/architect/tools-gitnexus)<a href="https://agentmods.dev/skills/alexei-led/architect/tools-gitnexus"><img src="https://agentmods.dev/badge/skills/alexei-led/architect/tools-gitnexus.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.00120 | $0.01050 |
| Opus 5 | $0.00060 | $0.00525 |
| Sonnet 5 | $0.00024 | $0.00210 |
| Haiku 4.5 | $0.00012 | $0.00105 |
Grade A, and why
tools-gitnexus 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitNexus
gitnexus turns git history into a queryable graph: co-change relationships,
per-file change frequency, and the historical blast radius of a path. It is the
evidence source for "do changes actually stay inside the intended boundary?" and
a corroborating signal for the volatility axis of Balanced Coupling — domain role
sets volatility; churn only supports it, it never sets it.
Evidence dimension: change.
When to use
Use to score change_locality (do edits respect module boundaries over history),
to ground volatility claims, and to find fragile seams where distant modules
co-change repeatedly. A module that churns and co-changes with a distant module
is a coupling risk only history can show. Build the index during the system-map
step.
Commands
Prefer exposed GitNexus runtime tools when available; use the CLI otherwise. Build or refresh indexes only in an approved writable cache/store.
gitnexus analyze # mine history → build the change graph
gitnexus status # index health + commit it covers
gitnexus list # entities/files known to the graph
gitnexus query "<expr>" # query co-change / frequency
gitnexus context <path> # what co-changes with <path>
gitnexus impact <path> # historical blast radius of a change
gitnexus detect-changes # files changed since the indexed commit
gitnexus cypher "<query>" # raw Cypher for custom graph questions
Flow: analyze, then status, then context / impact / cypher for
co-change evidence.
Stale-index handling
Run gitnexus status (and detect-changes) before trusting output. If the
index lags the working tree, co-change data is incomplete:
- Re-run
gitnexus analyzeto refresh, only if it can write to an approved cache/store. - If you cannot refresh, the change dimension is
tools_failed("stale index") — do not score change locality from it.
Evidence output
Record:
dimension: change.source: GitNexus status/freshness, query/context/impact command, and history window.facts: co-change pairs, churn hotspots, historical blast radius, or confirmed absence.limits: stale index, shallow clone, rename split, short history window, or failed analysis.
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 · 105 lines · 120 tokens per session scan A a3b08271da3e
tools-gitnexus is a skill published in the GitHub repository alexei-led/architect (2 stars, last pushed 1mo ago), licensed MIT. It adds 120 tokens to every session and 1,050 once invoked, about $0.0006 per session on Opus 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-31.
Other skills, from other repositories
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
daily-paper-generator
Use when the user asks to generate daily paper digests on a general topic. This skill supports both arXiv and bioRxiv (or either one), then produces structured Chinese/English summaries for selected papers.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
map-wayfind
Decision-frontier wayfinding: build and work a durable map of open design decisions BEFORE planning, for large or foggy efforts where /map-plan would force premature decomposition. Use when a task is too big or too vague to decompose — many unknowns, tangled decisions, or "I'm not even sure what to build yet" — and…
clipboard
Copy text to clipboard with optional rich formatting. Triggers on "copy to clipboard", "copy that", "pbcopy", "copy formatted", "copy rich text".