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 skills add azmym/agent-skills --skill setup-checkgit clone --depth 1 https://github.com/azmym/agent-skillsWrote 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/azmym/agent-skills/setup-check)<a href="https://agentmods.dev/skills/azmym/agent-skills/setup-check"><img src="https://agentmods.dev/badge/skills/azmym/agent-skills/setup-check.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.1 | $0.00144 | $0.07392 |
| Opus 5 | $0.00072 | $0.03696 |
| Sonnet 5 | $0.00029 | $0.01478 |
| Haiku 4.5 | $0.00014 | $0.00739 |
Grade A, and why
setup-check scanned grade A with 2 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 7d 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.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- `~/.claude/settings.json` > `enabledPlugins` (enabled/disabled state) Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Enumerates other installed skillslowAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
1. **Broken symlinks:** `ls -la ~/.claude/skills/` and verify each target exists Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 493 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Check
Audit Claude Code configuration and report issues, overlaps, update status, and cleanup recommendations.
Arguments
Parse from $ARGUMENTS. Default: all.
| Arg | Scope |
|---|---|
all |
Full audit (all categories below, including updates) |
updates |
Claude Code CLI + plugin version/update checks |
skills |
Skills: duplicates, broken symlinks, unused, placeholders |
hooks |
Hooks: conflicts, broken paths, event collisions |
plugins |
Plugins: disabled, stale cache, version tracking |
rules |
Rules: contradictions, overlap with plugin behavior |
settings |
Settings files: duplicates, conflicting keys (health only) |
security |
Security: broad permissions, skipped prompts, orphaned MCP perms |
mcp |
MCP servers: empty configs, duplicate servers |
memory |
Memory: empty dirs, stale entries, index mismatches |
overlaps |
Cross-category overlap detection only |
bedrock |
Bedrock config: recommended Bedrock-compatible options not currently set |
Multiple args supported: /setup-check skills plugins runs both.
Goal Message
In addition to category args, the user can pass a quoted free-text string as a goal message:
/setup-check "ready for production?"
/setup-check settings "security hardening"
If an argument is not a recognized category keyword, treat it as a goal message. The goal triggers an additional Goal Assessment section in the output (see below).
Scan Paths (MANDATORY)
You MUST read ALL of these paths for the relevant category. Do not skip any. Missing a path means missing findings.
Updates:
- Claude Code CLI binary (run
claude --versionto get current version) - npm registry (run
npm view @anthropic-ai/claude-code version 2>/dev/nullfor latest published version; requires network) ~/.claude/plugins/installed_plugins.json(plugin versions,gitCommitSha,lastUpdated)~/.claude/plugins/cache/(all cached versions; detect stale ones not matching activeinstallPath)claude plugins update <name>@<marketplace> -s <scope>output (authoritative source for update availability; the scope flag is required and must come from each plugin'sscopefield ininstalled_plugins.json)~/.claude/plugins/known_marketplaces.json(installed marketplaces with per-marketplacelastUpdatedtimestamps; used to detect which marketplaces changed after a refresh)claude plugin marketplace list --jsonoutput (authoritative current marketplace set; read-only)
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 493 lines · 144 tokens per session scan A e6553455adfe
setup-check is a skill published in the GitHub repository azmym/agent-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 144 tokens to every session and 7,392 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 2 findings (reads agent configuration directories, enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
ha-logs
A read-only troubleshooting skill for querying Hope Agent’s local SQLite databases, which store logs, conversations, and background-job status.
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.
bug-report
Creates a structured bug report from a description, or analyzes code to identify potential bugs. Ensures every bug report has full reproduction steps, severity assessment, and context.