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 metagit-ai/metagit-cli --skill metagit-gitnexusgit clone --depth 1 https://github.com/metagit-ai/metagit-cliWrote 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/metagit-ai/metagit-cli/metagit-gitnexus)<a href="https://agentmods.dev/skills/metagit-ai/metagit-cli/metagit-gitnexus"><img src="https://agentmods.dev/badge/skills/metagit-ai/metagit-cli/metagit-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.1 | $0.00042 | $0.00758 |
| Opus 5 | $0.00021 | $0.00379 |
| Sonnet 5 | $0.00008 | $0.00152 |
| Haiku 4.5 | $0.00004 | $0.00076 |
Grade A, and why
metagit-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 8d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Running GitNexus Analysis
Use this skill whenever GitNexus context is stale or missing for target repositories.
Local Wrapper (Use First)
./skills/metagit-gitnexus/scripts/analyze-targets.sh <workspace_root> [project_name]
Workflow
- Analyze the current repository where the command is run.
- Resolve target project repositories from
.metagit.yml. - Run
npx gitnexus analyzein each local repository path found. - Report per-repository success/failure and next actions.
Manual workspace graph (.metagit.yml → Cypher)
CLI flags: script -c and metagit config graph export -c .metagit.yml point at the manifest. --workspace-root is only the scan root for suggest; global metagit -c is appconfig.
Promote inferred edges first (see metagit-graph-maintain skill), then ingest:
./skills/metagit-gitnexus/scripts/ingest-workspace-graph.sh -c .metagit.yml
./skills/metagit-gitnexus/scripts/ingest-workspace-graph.sh -c .metagit.yml --gitnexus-repo my-umbrella --dry-run
Manual export + MCP:
metagit config graph export -c .metagit.yml --format tool-calls --output /tmp/graph-tool-calls.json
uv run python ./skills/metagit-gitnexus/scripts/ingest_workspace_graph.py /tmp/graph-tool-calls.json
# MCP export: metagit_export_workspace_graph_cypher
Schema DDL (MetagitEntity / MetagitLink) runs once per index; pass --gitnexus-repo when the umbrella index name differs from manifest name.
GitNexus group sync (cross-index analysis)
Align workspace.projects[] repos with a GitNexus group for group impact, group query, and contract linking:
./skills/metagit-gitnexus/scripts/sync-group.sh -c .metagit.yml
metagit gitnexus group sync -c .metagit.yml --json
metagit gitnexus group sync -c .metagit.yml --group-name my-workspace --prune
MCP: metagit_gitnexus_group_sync
Prerequisites:
- Each managed repo checkout exists locally and has been analyzed (
gitnexus analyze). - Registry entries exist in
~/.gitnexus/registry.jsonfor those paths. - Multi-repo workspace with
workspace.projects[]in.metagit.yml.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 82 lines · 42 tokens per session scan A 22e078ef4e14
metagit-gitnexus is a skill published in the GitHub repository metagit-ai/metagit-cli (3 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 758 once invoked, about $0.0002 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
perseus
Use when you need a bounded, local Perseus context render before an assistant reads project state. Perseus resolves selected workspace inputs such as git, services, sessions, and task notes into markdown. Use for deterministic session starts, workspace audits, and explicit context handoffs.
pypi-release
This skill should be used when releasing tunacode-cli to PyPI. It keeps the existing local release checks, then hands the actual PyPI upload to a GitHub Actions workflow that uses the repository's PYPIAPITOKEN secret.
memory-commit
Use when the user explicitly says "remember this", "save this", "ghi nho", "luu lai", "save for next time", or otherwise asks to persist the immediately preceding context. Captures with the appropriate contexttype (decision, preference, fact, skill, task, conversation) so future sessions can retrieve it accurately.
agentic-preflight
Use when shipping a branch — reviewing, documenting, linting, testing, and pushing work behind a quality gate. Also use when a push is blocked by the agentic-preflight pre-push hook or when the user says agentic-preflight:uninstall to remove this tool from the current project.
daf-git
GitHub/GitLab issue operations (update, link) with Markdown syntax reference and gh/glab CLI guide.
daf-workflow
DevAIFlow session context loader — reads session metadata, issue tracker tickets, and context files. Auto-activates when DAFSESSIONNAME is set. Also useful when asked about current task, session status, or workflow steps for daf open, daf new, daf git new, daf jira new, and daf investigate.