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 skills/dvnghiem/flowdeck/security-scannpx skills add DVNghiem/FlowDeck --skill security-scangit clone --depth 1 https://github.com/DVNghiem/FlowDeckWhat 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.00035 | $0.00726 |
| Opus 5 | $0.00017 | $0.00363 |
| Sonnet 5 | $0.00007 | $0.00145 |
| Haiku 4.5 | $0.00003 | $0.00073 |
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 3d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Scan Skill
Catches security issues before they reach production. Returns a severity-ranked report with specific remediations.
When to Activate
Activate:
- Before merging any PR that touches auth, data access, or API routes
- Before every production deployment
- When adding new dependencies
- When changing environment variable handling
Core Principles
- Security takes priority over convenience
- Every finding includes a specific remediation
- CRITICAL or HIGH = must fix before merge
- No exceptions without documented risk acceptance
Workflow
- Check for hardcoded secrets (grep patterns)
- Check for injection vulnerabilities (SQL, command, template)
- Verify auth middleware on protected routes
- Check input validation at API boundaries
- Run
npm audit --audit-level=moderate - Review sensitive data in logs
- Produce verdict
OWASP Top 10 Quick Reference
| ID | Name | Check For |
|---|---|---|
| A01 | Broken Access Control | Missing auth checks, IDOR, privilege escalation |
| A02 | Cryptographic Failures | HTTP for sensitive data, MD5/SHA1 for passwords |
| A03 | Injection | SQL/NoSQL/cmd/template injection via string concat |
| A04 | Insecure Design | Missing rate limiting, no lockout after failed logins |
| A05 | Security Misconfiguration | Debug mode in prod, default credentials, verbose errors |
| A06 | Vulnerable Components | CVEs in dependencies (run npm audit) |
| A07 | Auth Failures | Missing middleware, weak JWT, no session invalidation |
| A08 | Integrity Failures | Missing input validation, unsafe deserialization |
| A09 | Logging Failures | Passwords/tokens in logs, insufficient logging |
| A10 | SSRF | User-controlled URLs fetched by server without validation |
Scan Commands
# Dependency vulnerabilities
npm audit --audit-level=moderate
# Hardcoded secrets (grep patterns)
grep -r "password\s*=\s*['\"]" src/ --include="*.ts"
grep -r "api_key\s*=\s*['\"]" src/ --include="*.ts"
grep -r "secret\s*=\s*['\"]" src/ --include="*.ts"
# SQL string concatenation
grep -r "query\`.*\${" src/ --include="*.ts"
grep -rn "query.*+.*req\." src/ --include="*.ts"
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.
- 3d ago First seen · 92 lines · 35 tokens per session scan A 85cafff17303
security-scan is a skill published in the GitHub repository DVNghiem/FlowDeck (24 stars, last pushed 14d ago), licensed MIT. It adds 35 tokens to every session and 726 once invoked, about $0.0002 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-30.
Other skills, from other repositories
oh-my-opencode-slim
Configure and improve oh-my-opencode-slim for the current user. Use when users want to tune agents, models, prompts, custom agents, skills, MCPs, presets, or plugin behavior. Also use when recurring workflow friction suggests a safe config or prompt improvement.
reflect
Review recent work, find repeated workflow patterns, and suggest reusable skills, agents, commands, config changes, or playbooks. Use when the user asks to learn from past sessions, improve recurring workflows, or identify what should be turned into reusable agent instructions.
clonedeps
Clone important project dependency source code into an ignored local workspace so OpenCode can inspect library internals. Use when the user asks to clone dependencies, inspect dependency/source internals, understand SDK/framework behavior from source, debug library implementation details, or make core dependency repos…
codemap
Generate comprehensive hierarchical codemaps for UNFAMILIAR repositories. Expensive operation - only use when explicitly asked for codebase documentation or initial repository mapping.
deepwork
High-cost orchestrator workflow for large, high-risk, multi-phase coding efforts with meaningful dependencies and review gates. Do not activate for routine multi-file changes.
worktrees
Manage Git worktrees as OMO safe isolated coding lanes for complex, risky, or parallel work.