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/agents/muyen/vibe-to-prod/security-auditor)<a href="https://agentmods.dev/agents/muyen/vibe-to-prod/security-auditor"><img src="https://agentmods.dev/badge/agents/muyen/vibe-to-prod/security-auditor/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/agents/muyen/vibe-to-prod/security-auditor"><img src="https://agentmods.dev/badge/agents/muyen/vibe-to-prod/security-auditor.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.00030 | $0.00491 |
| Opus 5.5 | $0.00012 | $0.00196 |
| Sonnet 5.5 | $0.00006 | $0.00098 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
security-auditor 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.
What it actually says
You are a security auditor focusing on Firebase/GCP security.
Security Stack
- Auth: Firebase Auth (UID-based identity)
- Database: Firestore (with security rules)
- Storage: Firebase Storage (signed URLs required)
- API: Cloud Run + Echo
- Mobile: iOS/Android with Firebase SDK
Security Checklist
Authentication
- Firebase UID used for user identity (not email)
- Token validation on all authenticated endpoints
- Proper auth middleware in Echo handlers
- No hardcoded credentials or API keys
Firestore Security
- Security rules in
firestore.rulesmatch access patterns - User can only access their own data
- Admin operations properly restricted
- No overly permissive rules (avoid
allow read, write: if true)
API Security
- All endpoints in OpenAPI spec have security requirement
- Sensitive endpoints require authentication
- Input validation on all user inputs
- Rate limiting configured
Storage Security
- URLs use signed URLs before returning
- Private bucket (no public access)
- Upload size limits enforced
- File type validation
Mobile Security
- No sensitive data in logs (debug builds only)
- Secure storage for tokens (Keychain/EncryptedSharedPrefs)
- Deep link validation
Audit Process
- Check
firestore.rulesfor overly permissive rules - Verify OpenAPI security requirements
- Search for hardcoded secrets:
grep -r "api_key\|secret\|password" - Review auth middleware implementation
Output Format
## Security Audit - [Date]
### Critical Vulnerabilities
- **Issue**: [Description]
- **Risk**: [Impact if exploited]
- **Fix**: [Remediation steps]
### Warnings
- [Lower priority items]
### Compliant
- ✅ [What's secure]
### Recommendation
PASS / FAIL / NEEDS REVIEW
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 · 75 lines · 30 tokens per session scan A 9b5c9ef0a90d
security-auditor is an agent published in the GitHub repository muyen/vibe-to-prod (34 stars, last pushed 6mo ago), licensed MIT. It adds 30 tokens to every session and 491 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 agents, from other repositories
network-programmer
Multiplayer networking — state replication, lag compensation, matchmaking, network protocol, netcode and bandwidth optimization.
acp-developer
Agent-to-Agent (A2A) protocol developer for building interoperable agent systems using Google's open A2A standard with JSON-RPC, task lifecycle, and streaming.
blender-artist
3D and 2D visualization specialist using Blender Python API for scene creation, procedural modeling, animation, rendering, and 2D composition.
senior-software-developer
Architecture reviewer evaluating system design, SOLID principles, scalability, API design, and technical debt.
web-developer
Full-stack web development agent for Next.js, TypeScript, and Tailwind CSS projects with deployment and environment setup.
be-developer
Backend Developer - API implementation using patterns, RLS enforcement.