A change-analysis skill that traces which other files depend on the files you are changing. It uses the project's dependency graph, which maps relationships such as imports and interface implementations.

Use it to identify direct and indirect consumers, assess the risk of a change, and review which modules or packages may need updates.

It shows the likely reach of a change before you commit it, including files affected indirectly through several dependency steps.

How ysfAskri/archguardian configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to ysfAskri/archguardian. 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/ysfAskri/archguardian/master/.claude/skills/impact/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/ysfAskri/archguardian

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ysfaskri/archguardian/impact/github.svg)](https://agentmods.dev/skills/ysfaskri/archguardian/impact)

Your own site

<a href="https://agentmods.dev/skills/ysfaskri/archguardian/impact"><img src="https://agentmods.dev/badge/skills/ysfaskri/archguardian/impact/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ysfaskri/archguardian/impact"><img src="https://agentmods.dev/badge/skills/ysfaskri/archguardian/impact.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 12 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 316 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 original No closer match found 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.

Model	Per session	Once invoked
Fable 5.1	$0.00012	$0.00316
Opus 5.5	$0.00005	$0.00126
Sonnet 5.5	$0.00002	$0.00063
Haiku 4.5	$0.00001	$0.00032

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

Security

Grade A, and why

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

.claude/skills/impact/SKILL.md · 42 lines

What it actually says

archguardian impact

Show the downstream impact of current file changes by analyzing the project's dependency graph.

Instructions

Run the scan with the impact analyzer enabled:

npx archguardian scan --format json $ARGUMENTS

Parse the JSON output and focus on the impact/downstream-consumers findings.
For each impacted file, explain:
- Which changed file causes the impact
- Which downstream files consume or depend on it
- The type of dependency (import, re-export, interface implementation, etc.)
- The risk level (how many transitive consumers are affected)
Summarize the total impact:
- Number of directly affected files
- Number of transitively affected files
- Which modules or packages are impacted
Offer to generate a visual diagram of the impact chain:
- Suggest running /diagram to see the full dependency structure
- Or /summarize to get a Mermaid diagram of the change impact

Tips

Impact analysis works best when run on staged or uncommitted changes.
If no changes are detected, suggest staging files first with git add.
For large impact chains, recommend scoping the analysis to specific directories.
Use this before merging PRs to understand the blast radius of changes.

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.

1mo ago First seen · 42 lines · 12 tokens per session scan A 53f52adf6011

Subscribe to this mod's changes

impact is a skill published in the GitHub repository ysfAskri/archguardian (4 stars, last pushed 8mo ago), licensed MIT. It adds 12 tokens to every session and 316 once invoked, about $0.0000 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-31.

Code review Debugging ai-code architecture ast cli code-quality conventions

argot-refresh

Refresh Argot's committed fit snapshot safely — first diagnose why maintenance is recommended, re-audit corpus scope and structural path changes, review stale mutes and policy entries with the user, then fit locally, verify, and prepare the reviewed .argot/ update. Use when argot status, argot check, MCP, or CI…

get-tmonier/argot · 136 tokens

arch-optimize

A software architecture review workflow that scans a codebase for structural risks and measures code quality. It checks issues such as overly complex code, repeated knowledge, changes spreading across many files, circular dependencies, and distorted domain models.

bfxh/arch-optimize · 114 tokens

skill

The HefestoAI agent skill moved to skills/hefestoai/ (name: hefestoai, following the Agent Skills specification). Its reference docs (commands.md, issuetypes.md, integration.md, semanticdrift.md, reliabilitydrift.md and analysis/) moved with it.

artvepa80/Agents-Hefesto · 0 tokens

cli-audit-code

Audit code quality with weighted scoring across 12 dimensions (naming, complexity, module design, DRY, errors, security, tests, architecture). Detects named anti-patterns (Fowler/Mantyla taxonomy). Use when reviewing code quality, auditing clean code compliance, checking for code smells, or saying 'audit code', 'code…

Destynova2/cli-code-skills · 92 tokens

codemap

Generate and incrementally maintain an interactive architecture map plus a per-module code-quality audit (health scores 0-100, smell findings, lines-of-code, and a clickable dependency graph) for any codebase. Use when the user wants to visualize a project's functional modules, audit or score code quality, check…

Asixa/codemap-skill · 153 tokens

refactor

Automated iterative code refactoring with swarm-orchestrated specialist agents including deep codebase discovery, confidence-scored code review, and security analysis. Use this skill when the user wants to improve existing code quality, clean up messy code, restructure, simplify, reduce tech debt, or perform…

zircote-plugins/refactor · 112 tokens

archguardian: Skill for Claude Code