scan

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

A project-wide code check that uses ArchGuardian to find problems and group them by severity.

In plain words
What is it for?
Run it to inspect a project, review the code behind each finding, and get suggested fixes. It can also report baselines, quality checks, and CI results when those options are used.
Why use it?
It turns a large scan into understandable findings, so you can see which issues matter most and how to address them.

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/scan
Any agent
npx skills add ysfAskri/archguardian --skill scan
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 scan

README.md
[![agentmods](https://agentmods.dev/badge/skills/ysfaskri/archguardian/scan.svg)](https://agentmods.dev/skills/ysfaskri/archguardian/scan)
Your own site
<a href="https://agentmods.dev/skills/ysfaskri/archguardian/scan"><img src="https://agentmods.dev/badge/skills/ysfaskri/archguardian/scan.svg" alt="Measured on agentmods" height="20"></a>
Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 348 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.00016 $0.00348
Opus 5 $0.00008 $0.00174
Sonnet 5 $0.00003 $0.00070
Haiku 4.5 $0.00002 $0.00035

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

Security

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 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/scan/SKILL.md · 35 lines

What it actually says

archguardian scan

Run a full project scan using archguardian and help the user understand and resolve findings.

Instructions

  1. Run the scan command:
    npx archguardian scan --format json $ARGUMENTS
    
  2. Parse the JSON output and present findings grouped by severity (errors first, then warnings, then info).
  3. For each finding, explain:
    • What the rule checks and why it matters
    • The specific code that triggered it
    • A concrete fix suggestion
  4. 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.
  5. If the user passed --update-baseline or --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 /fix for auto-fixable issues or /suppress for false positives.
  • Offer to run /baseline if this is a first-time adoption with many existing findings.
  • Use --quality-gate to enforce quality thresholds and get a pass/fail result (see /gate).
  • Use --ci github in CI pipelines to output findings as GitHub Actions annotations.
  • Use --post-to-pr to post findings as inline review comments on a GitHub PR (requires GITHUB_TOKEN).
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 · 35 lines · 16 tokens per session scan A 6109a85454e8

Subscribe to this mod's changes

scan is a skill published in the GitHub repository ysfAskri/archguardian (4 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 348 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.