DashClaw: Skill for Claude Code

.agents/skills/gitnexus-impact-analysis/SKILL.md

gitnexus-impact-analysis is a skill for Claude Code, Codex from ucsandman/DashClaw. It costs 50 tokens per session (1,777 once invoked), scanned A, a copy of gitnexus-impact-analysis, MIT.

A GitNexus guide for checking which parts of a codebase depend on something before changing it. GitNexus maps direct and indirect dependencies and affected execution flows.

In plain words
What is it for?
Use it to assess callers and importers, review affected flows, inspect current changes, and decide what needs testing before a code change.
Why use it?
It shows the likely blast radius of a change so developers can identify breakage risks before editing or committing code.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is ucsandman/DashClaw's own configuration. It tells Claude Code and Codex how to work on DashClaw itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything DashClaw configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ucsandman/DashClaw. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ucsandman/DashClaw/main/.agents/skills/gitnexus-impact-analysis/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/ucsandman/DashClaw

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for gitnexus-impact-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/ucsandman/dashclaw/gitnexus-impact-analysis/github.svg)](https://agentmods.dev/skills/ucsandman/dashclaw/gitnexus-impact-analysis)
Your own site
<a href="https://agentmods.dev/skills/ucsandman/dashclaw/gitnexus-impact-analysis"><img src="https://agentmods.dev/badge/skills/ucsandman/dashclaw/gitnexus-impact-analysis/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.

agentmods 80×15 button for gitnexus-impact-analysis

Your own site · 80×15
<a href="https://agentmods.dev/skills/ucsandman/dashclaw/gitnexus-impact-analysis"><img src="https://agentmods.dev/badge/skills/ucsandman/dashclaw/gitnexus-impact-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,777 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00050 $0.01777
Opus 5.5 $0.00020 $0.00711
Sonnet 5.5 $0.00010 $0.00355
Haiku 4.5 $0.00005 $0.00178

Measured 1mo ago against content hash 5e09acc141b1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

gitnexus-impact-analysis 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 1mo 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.

Origin

This is a copy

100% identical to gitnexus-impact-analysis — 90 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.

.agents/skills/gitnexus-impact-analysis/SKILL.md · 168 lines

How it starts

The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Impact Analysis with GitNexus

When to Use

  • "Is it safe to change this function?"
  • "What will break if I modify X?"
  • "Show me the blast radius"
  • "Who uses this code?"
  • Before making non-trivial code changes
  • Before committing — to understand what your changes affect

Bind the repository first

Impact analysis is the gate that authorizes an edit, so it must answer for the repository you are about to edit.

Call list_repos {} before the first tool call. With one indexed repository, use the examples below as written. With more than one, pass repo on every call: an omitted repo normally errors, but under an MCP policy with a configured default it resolves to that default silently. If you cannot tell which repository is meant, stop and ask — every result below an ambiguous identity inherits the ambiguity. list_repos is paginated, so page with offset: pagination.nextOffset until hasMore is false before concluding a repository is absent.

detect_changes takes worktree when your changes are in a linked worktree the MCP server was not launched from. The server auto-detects a worktree only when it was launched from inside one; otherwise git diff runs in the wrong checkout and reports zero changed symbols — a false clean check that carries none of the degradation flags described below. In the CLI fallbacks, --repo . means the current checkout; pass the intended repository path instead when you are not standing in it.

State the bound identity with your risk report:

Repository: <name> (<path>)   Worktree: <path>   Index: <commit>, <n> behind HEAD

Workflow

0. list_repos {}                                           → Bind repo (and worktree)
1. impact({target: "X", direction: "upstream"}) or `node .gitnexus/run.cjs impact "X" --direction upstream --repo .`
2. READ gitnexus://repo/{name}/processes                   → Check affected execution flows
3. detect_changes({scope: "all"}) or `node .gitnexus/run.cjs detect-changes --scope all --repo .`
4. Assess risk and report to user, echoing repo/worktree/index identity

Read the full file on GitHub · 168 lines

Changes

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.

  1. 1mo ago Changed · +70 lines 5e09acc141b1
  2. 1mo ago First seen · 98 lines · 50 tokens per session scan A 09e529505da1

Subscribe to this mod's changes

gitnexus-impact-analysis is a skill published in the GitHub repository ucsandman/DashClaw (313 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 1,777 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to gitnexus-impact-analysis, differing in 90 lines, and is treated as a copy.