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 agentmods add commands/afaizalam2003/master-claude-skill/security-scangit clone --depth 1 https://github.com/afaizalam2003/Master-claude-skillWrote 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/commands/afaizalam2003/master-claude-skill/security-scan)<a href="https://agentmods.dev/commands/afaizalam2003/master-claude-skill/security-scan"><img src="https://agentmods.dev/badge/commands/afaizalam2003/master-claude-skill/security-scan.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 | $0.00008 | $0.00160 |
| Opus 5 | $0.00004 | $0.00080 |
| Sonnet 5 | $0.00002 | $0.00032 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
security-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.
This is a copy
100% identical to security-scan — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
- Ensure dependencies are installed:
pip install safety==3.2.4 brew install gitleaks # or appropriate package manager - Scan for committed secrets:
gitleaks detect --verbose --redact- Resolve any findings before continuing.
- Audit Python dependencies (if requirements files exist):
for f in $(find . -name "requirements*.txt" 2>/dev/null); do safety check --full-report --file "$f" done - Record results in the commit template's Testing section.
- After a clean pass, proceed with commit and push workflow.
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.
- 4d ago First seen · 23 lines · 8 tokens per session scan A 24bedfc4a7f1
security-scan is a command published in the GitHub repository afaizalam2003/Master-claude-skill (2 stars, last pushed 5mo ago), licensed MIT. It adds 8 tokens to every session and 160 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to security-scan, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
Diagnose
Run a 20-point health check across the plugin install, project config, PM/notification reachability, docs freshness, board consistency, and git state. Read-only — never changes state. Reports each check as PASS/WARN/FAIL/SKIP with an actionable fix. Target under 15 seconds end-to-end. Use before demos, after a plugin…
status
Alias for /work-state — report a slug's position in the scope chain (envision→spec→draft-plan→blueprint→execute→archive) as deterministic structured state. Read-only.
unity-feature
Plans and implements a Unity feature — identifies subsystems, loads skills, writes code, sets up scene elements via MCP.
unity-fix
Diagnoses and fixes a Unity bug — reads console errors, checks common causes, applies targeted fix, verifies via MCP.
consolidate-triggers
Wraps agents/trigger-consolidator/AGENT.md. Finds every trigger on a given sObject and produces a single-handler migration plan using templates/apex/TriggerHandler.cls + TriggerControl.cls.
audit-validation-rules
/audit-router --domain validationrule --object --target-org.