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.
curl -O https://raw.githubusercontent.com/ysfAskri/archguardian/master/.claude/skills/summarize/SKILL.mdgit 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/summarize)<a href="https://agentmods.dev/skills/ysfaskri/archguardian/summarize"><img src="https://agentmods.dev/badge/skills/ysfaskri/archguardian/summarize/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.
<a href="https://agentmods.dev/skills/ysfaskri/archguardian/summarize"><img src="https://agentmods.dev/badge/skills/ysfaskri/archguardian/summarize.svg" alt="Reviewed on agentmods" width="80" 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.00012 | $0.00325 |
| Opus 5.5 | $0.00005 | $0.00130 |
| Sonnet 5.5 | $0.00002 | $0.00065 |
| Haiku 4.5 | $0.00001 | $0.00032 |
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 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.
What it actually says
archguardian summarize
Generate a visual summary of current changes and their impact across the project.
Instructions
-
Run the summarize command:
npx archguardian summarize --format mermaid $ARGUMENTS -
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>
- Suggest staging files first with
-
Show the Mermaid diagram output to the user in a fenced code block:
<output from command> -
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
-
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
/gateto check if the changes meet quality thresholds. - Pair with
/checkto see specific findings in the changed files.
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 · 45 lines · 12 tokens per session scan A f7981b753822
summarize 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 325 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.
Other skills, from other repositories
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…
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.
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.
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…
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…
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…