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/muyen/vibe-to-prodWrote 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/muyen/vibe-to-prod/security-scan)<a href="https://agentmods.dev/commands/muyen/vibe-to-prod/security-scan"><img src="https://agentmods.dev/badge/commands/muyen/vibe-to-prod/security-scan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/muyen/vibe-to-prod/security-scan"><img src="https://agentmods.dev/badge/commands/muyen/vibe-to-prod/security-scan.svg" alt="Reviewed on agentmods" width="80" 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.00017 | $0.00994 |
| Opus 5.5 | $0.00007 | $0.00398 |
| Sonnet 5.5 | $0.00003 | $0.00199 |
| Haiku 4.5 | $0.00002 | $0.00099 |
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 12d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Scan
Security scan for: $ARGUMENTS
Scan Scope
Backend (Go) Security Checks
- Hardcoded Secrets: Search for API keys, tokens, passwords in code
- SQL/NoSQL Injection: Check database queries for unsafe inputs
- Auth Bypass: Verify authentication middleware on protected routes
- Input Validation: Check for missing validation at API boundaries
- Dependencies: Check for known vulnerabilities
iOS (Swift) Security Checks
- Hardcoded Secrets: Search for API keys in code
- Insecure Storage: Check for Keychain usage vs UserDefaults
- Network Security: Verify ATS settings in Info.plist
- Debug Code: Check for print statements with sensitive data
Android (Kotlin) Security Checks
- Hardcoded Secrets: Search for API keys in code
- Insecure Storage: Check for EncryptedSharedPreferences usage
- Network Security: Check for cleartext traffic settings
- ProGuard/R8: Verify obfuscation for release builds
Quick Scan Commands
Backend:
# Check for hardcoded secrets
grep -rn --include="*.go" -E "(api[_-]?key|secret|password|token)\s*[:=]\s*\"[^\"]+\"" backend/
# Check for potential SQL injection (if using raw queries)
grep -rn --include="*.go" "fmt.Sprintf.*SELECT\|fmt.Sprintf.*INSERT\|fmt.Sprintf.*UPDATE" backend/
iOS:
# Check for hardcoded secrets
grep -rn --include="*.swift" -E "(api[_-]?key|secret|password|token)\s*[:=]\s*\"[^\"]+\"" mobile/ios/
# Check for UserDefaults with sensitive data
grep -rn --include="*.swift" "UserDefaults.*password\|UserDefaults.*token\|UserDefaults.*key" mobile/ios/
Android:
# Check for hardcoded secrets
grep -rn --include="*.kt" -E "(api[_-]?key|secret|password|token)\s*[:=]\s*\"[^\"]+\"" mobile/android/
# Check for SharedPreferences with sensitive data
grep -rn --include="*.kt" "SharedPreferences.*password\|SharedPreferences.*token" mobile/android/
Instructions
- Run appropriate security checks based on argument (backend, ios, android, or all)
- Report findings by severity:
- 🔴 Critical: Immediate action required
- 🟠 High: Should fix before release
- 🟡 Medium: Should fix soon
- 🟢 Low: Consider fixing
- Provide specific file:line references
- Suggest remediations for each issue
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.
- 12d ago First seen · 150 lines · 17 tokens per session scan A 31e1766d593d
security-scan is a command published in the GitHub repository muyen/vibe-to-prod (34 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 994 once invoked, about $0.0001 per session on Opus 5.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-10-04.
Other commands, from other repositories
clarify
Reduce spec ambiguity via targeted questions with adaptive auto-invocation (planning is 80% of success).
ultrathink
Enter deep craftsman mode - question everything, plan like Da Vinci, craft insanely great solutions, then materialize to roadmap.
init
Initialize project documentation, preferences, or design tokens.
quick-fix
Fast-track workflow for small bug fixes.
help
Category: System Syntax: /help [command|topic].
plan-status
Render the current plan tree. Alias for /aura-frog:plan status (v3.7.2+).