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/scan/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/scan)<a href="https://agentmods.dev/skills/ysfaskri/archguardian/scan"><img src="https://agentmods.dev/badge/skills/ysfaskri/archguardian/scan/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/scan"><img src="https://agentmods.dev/badge/skills/ysfaskri/archguardian/scan.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.00016 | $0.00348 |
| Opus 5.5 | $0.00006 | $0.00139 |
| Sonnet 5.5 | $0.00003 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
scan 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 scan
Run a full project scan using archguardian and help the user understand and resolve findings.
Instructions
- Run the scan command:
npx archguardian scan --format json $ARGUMENTS - Parse the JSON output and present findings grouped by severity (errors first, then warnings, then info).
- For each finding, explain:
- What the rule checks and why it matters
- The specific code that triggered it
- A concrete fix suggestion
- If there are many findings, summarize the top issues and ask if the user wants to see details for a specific file or rule category.
- If the user passed
--update-baselineor--baseline, include those flags in the command.
Tips
- If the scan returns 0 issues, congratulate the user.
- If there are suppressed or baseline counts in the output, mention them.
- Offer to run
/fixfor auto-fixable issues or/suppressfor false positives. - Offer to run
/baselineif this is a first-time adoption with many existing findings. - Use
--quality-gateto enforce quality thresholds and get a pass/fail result (see/gate). - Use
--ci githubin CI pipelines to output findings as GitHub Actions annotations. - Use
--post-to-prto post findings as inline review comments on a GitHub PR (requires GITHUB_TOKEN).
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 · 35 lines · 16 tokens per session scan A 6109a85454e8
scan is a skill published in the GitHub repository ysfAskri/archguardian (4 stars, last pushed 8mo ago), licensed MIT. It adds 16 tokens to every session and 348 once invoked, about $0.0001 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
roam
Codebase comprehension via roam-code CLI. Use when exploring codebases, planning modifications, debugging failures, assessing PR risk, or checking architecture health. Triggers on: understanding project structure, pre-change safety checks, finding symbols/files, blast radius analysis, affected tests, health scoring…
sipcode-regress
Check the user's own local Claude Code and Codex logs for regressions after an update (prompt-cache misses, 5-minute cache TTL, uncached context, hourly cache rebuilds, Codex usage limit draining faster per token) and pin each one to the version that introduced it, using the Sipcode CLI. Use when the user asks whether…
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…
module-federation
Add, review, or debug client-rendered Module Federation support in Rsbuild-first TypeScript applications. Covers host/remote roles, exposes, remotes, shared dependencies, generated types, runtime loading failures, and observability checks.
static-code-analysis
Selects, configures, and integrates a static analysis tool for the project's language. Covers tool selection, rule configuration, CI integration, fixing existing violations, and pre-commit hook setup. Invoked when the user asks to add linting, set up static analysis, or configure a code quality tool.
fix-bug
Investigates and fixes a reported bug. Reads relevant code, identifies the root cause, proposes a fix, and adds or updates tests to prevent regression. Invoked when the user describes unexpected behavior, an error, a crash, or a failing test.