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.
git clone --depth 1 https://github.com/smithdak/claude-marketplaceWrote 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/smithdak/claude-marketplace/security-scan)<a href="https://agentmods.dev/commands/smithdak/claude-marketplace/security-scan"><img src="https://agentmods.dev/badge/commands/smithdak/claude-marketplace/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.1 | $0.00018 | $0.00829 |
| Opus 5 | $0.00009 | $0.00415 |
| Sonnet 5 | $0.00004 | $0.00166 |
| Haiku 4.5 | $0.00002 | $0.00083 |
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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Optimizely Security Scan Command
Preview what files will be analyzed and identify potential sensitive content before running full analysis.
Usage
/optimizely:security-scan # Run security preview
/optimizely:security-scan --preview # Detailed file listing
What It Does
The security-scan command:
- Lists Analysis Scope - Shows which files and directories will be analyzed
- Identifies Sensitive Files - Flags files that may contain secrets
- Checks .claudeignore - Verifies exclusion patterns
- Recommends Exclusions - Suggests files to exclude
Analysis Scope
Files that WILL be analyzed:
*.cs - C# source files
*.csproj - Project files
*.cshtml - Razor views
*.json - Configuration (with caution)
*.md - Documentation
Files that SHOULD be excluded:
appsettings.*.json - May contain connection strings
*.pfx, *.p12 - Certificates
*.key - Private keys
**/secrets/** - Secret files
connectionStrings.config - Database credentials
Sensitive File Detection
Scans for potentially sensitive content:
High Risk Files
**/connectionStrings.config
**/appsettings.Production.json
**/appsettings.Development.json
**/*.pfx
**/*.p12
**/*.key
**/*.pem
**/secrets/**
**/.env
**/*.env.*
Medium Risk Patterns
Grep: password\s*[:=]
Grep: connectionstring\s*[:=]
Grep: apikey\s*[:=]
Grep: secret\s*[:=]
Grep: -----BEGIN.*KEY-----
Output Format
Optimizely Security Scan
Project: MyOptimizelyProject
Path: /src/MyProject
=== Analysis Scope ===
Directories to analyze:
✓ src/Web/Controllers/ (15 files)
✓ src/Web/Views/ (45 files)
✓ src/Core/Models/ (25 files)
✓ src/Core/Services/ (12 files)
Files to analyze: 142 total
=== Sensitive File Check ===
⚠️ Potentially sensitive files found:
HIGH RISK:
- appsettings.Development.json (may contain local secrets)
- appsettings.Production.json (may contain production secrets)
MEDIUM RISK:
- src/Web/Startup.cs (contains connection string reference)
=== .claudeignore Status ===
❌ No .claudeignore file found
Recommended .claudeignore content:
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.
- 6d ago First seen · 164 lines · 18 tokens per session scan A cfad2f253be3
security-scan is a command published in the GitHub repository smithdak/claude-marketplace (3 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 829 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.