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/ysfaskri/archguardian/impactnpx skills add ysfAskri/archguardian --skill impactgit clone --depth 1 https://github.com/ysfAskri/archguardianWrote 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/ysfaskri/archguardian/impact)<a href="https://agentmods.dev/skills/ysfaskri/archguardian/impact"><img src="https://agentmods.dev/badge/skills/ysfaskri/archguardian/impact.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.00012 | $0.00316 |
| Opus 5 | $0.00006 | $0.00158 |
| Sonnet 5 | $0.00002 | $0.00063 |
| Haiku 4.5 | $0.00001 | $0.00032 |
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 5d 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.
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-consumersfindings. -
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
/diagramto see the full dependency structure - Or
/summarizeto get a Mermaid diagram of the change impact
- Suggest running
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.
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.
- 5d ago First seen · 42 lines · 12 tokens per session scan A 53f52adf6011
impact is a skill published in the GitHub repository ysfAskri/archguardian (4 stars, last pushed 6mo ago), licensed MIT. It adds 12 tokens to every session and 316 once invoked, about $0.0001 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
code-to-diagram
Analyze codebases and automatically generate architecture diagrams, flowcharts, and org charts. Uses AST parsing to map import dependencies for Python, JS/TS, Go, and Java, outputting Mermaid or SVG files. Triggered when users ask to visualize code architecture, understand dependencies, draw a flowchart, or create a…
truecourse-hooks
Install, configure, or remove the TrueCourse pre-commit hook.
truecourse-analyze
Run TrueCourse architecture analysis on this repository.
truecourse-fix
Fix TrueCourse violations that have suggested fixes.
truecourse-list
List TrueCourse violations found in this repository.
refactoring-workflow
Improve the structure of existing code without changing its behaviour, in small verified steps under a green test suite. Use when the user asks to refactor, clean up, restructure or simplify code, wants to reduce duplication or coupling, is preparing a codebase for a feature it cannot currently accommodate, or when…