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/latestaiagents/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/commands/latestaiagents/agent-skills/security-scan)<a href="https://agentmods.dev/commands/latestaiagents/agent-skills/security-scan"><img src="https://agentmods.dev/badge/commands/latestaiagents/agent-skills/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.00011 | $0.00414 |
| Opus 5 | $0.00005 | $0.00207 |
| Sonnet 5 | $0.00002 | $0.00083 |
| Haiku 4.5 | $0.00001 | $0.00041 |
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.
What it actually says
/security-scan
Scan your codebase for common security vulnerabilities.
What I Need
Tell me:
- What language/framework is your project?
- Any specific concerns (auth, API, data handling)?
- Scope: full scan or specific files?
Scan Coverage
OWASP Top 10 Checks
- A01 - Injection - SQL, NoSQL, Command injection
- A02 - Broken Auth - Session management, passwords
- A03 - Sensitive Data - Encryption, data exposure
- A04 - XXE - XML processing vulnerabilities
- A05 - Access Control - Authorization flaws
- A06 - Misconfig - Security settings, defaults
- A07 - XSS - Cross-site scripting
- A08 - Deserialization - Unsafe object handling
- A09 - Vulnerable Components - Dependencies
- A10 - Logging - Insufficient monitoring
Scan Process
Step 1: Static Analysis
I'll search for vulnerable patterns in your code:
- String concatenation in queries
- Eval/exec with user input
- Hardcoded secrets
- Missing input validation
Step 2: Dependency Check
I'll review your dependencies:
- Known CVEs
- Outdated packages
- Unused dependencies
Step 3: Configuration Review
I'll check security settings:
- CORS configuration
- Security headers
- Cookie settings
- Environment variables
Output
I'll provide:
- Severity-ranked findings
- Specific file:line locations
- Fix recommendations with code examples
- Links to relevant documentation
Quick Commands
# Run with Semgrep
semgrep --config=p/owasp-top-ten .
# Check dependencies (npm)
npm audit
# Check dependencies (Python)
pip-audit
# Scan secrets
gitleaks detect --source .
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 · 76 lines · 11 tokens per session scan A 28a0759ebc55
security-scan is a command published in the GitHub repository latestaiagents/agent-skills (5 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 414 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-09-03.
Other commands, from other repositories
fdk-react-create
Create a new Platform 3.0 React Meta app (default UI stack). Uses fdk create react-starter-template or react-meta skeletons with DEW components, metaConfig in manifest.json, and React Router.
fdk-refactor
Reduce function complexity in a Freshworks app to meet cyclomatic complexity ≤ 7 per function. Extracts helper functions, simplifies conditionals, and preserves behavior while improving code quality.
fw-setup-uninstall
Uninstall FDK completely — keeps Node.js and nvm (/fw-setup uninstall).
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.