summarize

summarize is a skill for Claude Code, Codex from ysfAskri/archguardian. It costs 12 tokens per session (325 once invoked), scanned A, original, MIT.

A visual summary of current code changes and the files they may affect. It produces a Mermaid diagram, a text format that can be rendered as a flowchart.

In plain words
What is it for?
Use it to show changed files, direct and indirect dependents, high-risk shared modules, and a diagram suitable for a GitHub pull request.
Why use it?
It turns a dependency chain into a diagram, making the breadth and risk of a change easier to review.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/ysfaskri/archguardian/summarize
Any agent
npx skills add ysfAskri/archguardian --skill summarize
Clone the repo
git clone --depth 1 https://github.com/ysfAskri/archguardian

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 summarize

README.md
[![agentmods](https://agentmods.dev/badge/skills/ysfaskri/archguardian/summarize.svg)](https://agentmods.dev/skills/ysfaskri/archguardian/summarize)
Your own site
<a href="https://agentmods.dev/skills/ysfaskri/archguardian/summarize"><img src="https://agentmods.dev/badge/skills/ysfaskri/archguardian/summarize.svg" alt="Measured on agentmods" 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 325 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00012 $0.00325
Opus 5 $0.00006 $0.00162
Sonnet 5 $0.00002 $0.00065
Haiku 4.5 $0.00001 $0.00032

Measured 4d ago against content hash f7981b753822, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

summarize 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 4d 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/summarize/SKILL.md · 45 lines

What it actually says

archguardian summarize

Generate a visual summary of current changes and their impact across the project.

Instructions

  1. Run the summarize command:

    npx archguardian summarize --format mermaid $ARGUMENTS
    
  2. If the command fails because there are no staged changes, tell the user:

    • Suggest staging files first with git add
    • Or specify files manually with --files <glob>
  3. Show the Mermaid diagram output to the user in a fenced code block:

    <output from command>
    
  4. Explain the impact chain shown in the diagram:

    • Which files were changed (source nodes)
    • Which files are directly affected (first-level dependents)
    • Which files are transitively affected (downstream consumers)
    • The overall blast radius of the changes
  5. Highlight any high-risk impacts:

    • Changes affecting many downstream consumers
    • Changes touching shared utilities or core modules
    • Changes crossing module or package boundaries

Tips

  • The Mermaid diagram can be pasted into GitHub PR descriptions for visual context.
  • For large projects, the diagram may be very wide — suggest scoping with --scope <glob> if needed.
  • Pair with /gate to check if the changes meet quality thresholds.
  • Pair with /check to see specific findings in the changed files.
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. 4d ago First seen · 45 lines · 12 tokens per session scan A f7981b753822

Subscribe to this mod's changes

summarize 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 325 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.