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 commands/imgompanda/fireauto/security-guardgit clone --depth 1 https://github.com/imgompanda/fireautoWhat 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.00019 | $0.02412 |
| Opus 5 | $0.00010 | $0.01206 |
| Sonnet 5 | $0.00004 | $0.00482 |
| Haiku 4.5 | $0.00002 | $0.00241 |
Grade A, and why
security-guard 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 2d 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 — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fireauto-secure - 보안 종합점검
코드베이스의 보안 취약점을 8개 카테고리로 종합 감사합니다. 실제 SaaS 프로젝트(pikome, ditfinder 등)에서 발견된 18개 취약점 패턴을 기반으로 설계되었습니다.
실행 절차
Step 1: 프로젝트 구조 파악
프로젝트 루트를 확인하고 기술 스택을 파악합니다.
- package.json 읽기 (프레임워크, 의존성 확인)
- 디렉토리 구조 스캔 (src/, app/, api/, pages/, lib/, utils/)
- .env 관련 파일 목록 확인
- next.config.*, middleware.* 파일 확인
Step 2: 8개 카테고리 보안 감사
각 카테고리별로 순차적으로 점검합니다. 발견된 모든 취약점을 수집합니다.
카테고리 1: 환경변수/시크릿 노출
점검 항목:
.env,.env.local,.env.production파일이.gitignore에 포함되어 있는지 확인- 소스코드 내 하드코딩된 API 키, 시크릿, 토큰 검색
NEXT_PUBLIC_접두사로 노출되면 안 되는 시크릿 확인- Supabase
service_role키가 클라이언트 코드에 노출되었는지 검색
검색 패턴:
Grep: "sk-", "sk_live", "sk_test" (API 키)
Grep: "password", "secret", "token" + "=" 또는 ":" (하드코딩)
Grep: "NEXT_PUBLIC_SUPABASE_SERVICE" (서비스 키 노출)
Grep: "supabaseAdmin", "createClient.*service_role" (admin 클라이언트 위치)
Glob: "**/.env*" (환경변수 파일)
심각도: CRITICAL
카테고리 2: 인증/인가 점검
점검 항목:
- API 라우트(
app/api/,pages/api/)에서 세션/인증 체크 누락 탐지 - admin 전용 라우트에서 권한 검증 여부
- Supabase admin 클라이언트(서비스롤)가 API 라우트 외부에서 사용되는지 확인
- RLS(Row Level Security) 우회 가능성: admin 클라이언트로 직접 DB 조작
- SECURITY DEFINER 함수에 입력값 검증이 있는지 확인
- middleware.ts/js의 보호 범위(matcher 패턴) 확인
- 인증 없이 접근 가능한 민감한 엔드포인트 탐지
검색 패턴:
Glob: "**/api/**/route.ts", "**/api/**/route.js"
Grep: "getSession", "getUser", "auth()", "getServerSession" (인증 함수)
Grep: "supabaseAdmin", "createServiceRoleClient" (admin 클라이언트)
Grep: "SECURITY DEFINER" (SQL 함수)
Read: middleware.ts (matcher 패턴 확인)
심각도: CRITICAL
카테고리 3: Rate Limiting
점검 항목:
- API 엔드포인트별 rate limit 적용 여부
- AI 관련 엔드포인트(OpenAI, Anthropic 호출)에 rate limit 필수 확인
- 비용 발생 엔드포인트(이메일 발송, 결제 처리)에 rate limit 확인
- rate limit 라이브러리 사용 여부 (upstash/ratelimit, express-rate-limit 등)
- 로그인/회원가입 엔드포인트의 브루트포스 방어
검색 패턴:
Grep: "ratelimit", "rateLimiter", "rate-limit", "RateLimit"
Grep: "openai", "anthropic", "claude", "gpt" (AI 호출 위치)
Grep: "resend", "sendEmail", "sendMail" (이메일 발송 위치)
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.
- 2d ago First seen · 281 lines · 19 tokens per session scan A ccea4d3bf482
security-guard is a command published in the GitHub repository imgompanda/fireauto (140 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 2,412 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-30.
Other commands, from other repositories
setup
Set up Postman MCP Server. Authenticate via OAuth or API key, verify connection, select workspace.
test
Run Postman collection tests, analyze results, diagnose failures, and suggest fixes.
get-flow-run
Inspect a Postman Flow run by its Run ID — per-block logs, failing block, and status.
warden-cost
Dollar accounting — what does each active rule actually save, in money? Translates the token-measured verdict into dollars using a price table and the agent's own token-type mix, with a per-session net and a break-even. Read-only; spends no tokens.
routine
Execute one maintenance routine defined in scv/routines/ .md (task + guardrails + exit-criteria contract), or list defined routines. SCV never schedules — pair with host features like /loop or cron yourself. Use whenever the user asks to run a recurring maintenance task, or asks what routines exist — not only when…
incident
Live incident response — intake a Sentry issue, stack trace, or symptom; gate mitigate-first vs root-cause-first; keep a UTC timeline. Use when production is broken RIGHT NOW; for the after-action write-up alone, use /orc:postmortem.