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/fireship-installgit 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.00018 | $0.01972 |
| Opus 5 | $0.00009 | $0.00986 |
| Sonnet 5 | $0.00004 | $0.00394 |
| Haiku 4.5 | $0.00002 | $0.00197 |
Grade C, and why
fireship-install scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .git How it starts
The opening of the file, as written. The whole thing — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fireauto-fireship-install: FireShip Starter Kit 자동 설치
FireShip Starter Kit(FireShipZip3) 보일러플레이트를 자동으로 설치하고, docs/llm.md 온보딩 가이드에 따라 초기 설정까지 도와주는 커맨드예요.
모든 출력은 **한국어(토스체)**로 작성해요.
Step 1: 설치 환경 확인
먼저 현재 환경을 확인하세요:
node --version
git --version
- Node.js 18 이상이 필요해요
- git이 설치되어 있어야 해요
환경이 준비되지 않았으면 사용자에게 설치 방법을 안내하세요.
Step 2: 프로젝트 이름 및 경로 결정
사용자에게 물어보세요:
프로젝트 이름을 정해주세요! (예: my-saas, my-app) 기본값: 현재 디렉토리에
FireShipZip3이름으로 생성돼요.
사용자가 이름을 지정하면 그 이름으로, 아니면 기본값으로 진행해요.
Step 3: 보일러플레이트 클론
git clone https://github.com/imgompanda/FireShipZip3.git {프로젝트이름}
cd {프로젝트이름}
클론이 완료되면 git 히스토리를 초기화해요:
rm -rf .git
git init
git add -A
git commit -m "Initial commit from FireShip Starter Kit"
Step 4: 패키지 매니저 확인 및 의존성 설치
사용자에게 물어보세요:
어떤 패키지 매니저를 쓸까요? (npm / yarn / pnpm / bun) 기본값: npm
선택한 패키지 매니저로 설치해요:
# npm인 경우
npm install
# pnpm인 경우
pnpm install
# yarn인 경우
yarn install
# bun인 경우
bun install
Step 5: 환경 변수 설정
.env.example 파일을 .env.local로 복사해요:
cp .env.example .env.local
사용자에게 안내하세요:
.env.local파일이 생성됐어요! 아래 키들을 설정해야 해요:필수 (이것만 있으면 기본 동작해요)
NEXT_PUBLIC_SUPABASE_URL— Supabase 프로젝트 URLNEXT_PUBLIC_SUPABASE_ANON_KEY— Supabase 공개 키SUPABASE_SERVICE_ROLE_KEY— Supabase 서비스 키결제 연동 (3가지 중 택 1)
NEXT_PUBLIC_PAYMENT_PROVIDER— 결제 프로바이더 선택 (lemon / paddle / toss, 기본: lemon)LemonSqueezy:
LEMONSQUEEZY_API_KEY,LEMONSQUEEZY_WEBHOOK_SECRETPaddle:
PADDLE_API_KEY,PADDLE_WEBHOOK_SECRET,PADDLE_ENVIRONMENT(sandbox/production)Toss:
TOSS_SECRET_KEY,TOSS_CLIENT_KEY,TOSS_WEBHOOK_SECRET이메일
RESEND_API_KEY— Resend API 키AI 기능
GOOGLE_GENERATIVE_AI_API_KEY— Gemini API 키각 서비스 설정 가이드는
docs/폴더에 있어요. 지금 바로 설정할 수도 있고, 나중에 해도 괜찮아요.
사용자가 키를 제공하면 .env.local 파일에 직접 입력해주세요.
제공하지 않으면 그냥 넘어가세요.
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 · 241 lines · 18 tokens per session scan C 6a54abc27e21
fireship-install is a command published in the GitHub repository imgompanda/fireauto (140 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 1,972 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
test
Run Postman collection tests, analyze results, diagnose failures, and suggest fixes.
deploy-flow
Deploy a Postman Flow so it becomes triggerable, proposing and confirming a trigger path.
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…
workspace
Set up or change this repo's place in a multi-repo SCV workspace: join an umbrella as a child, create an umbrella (root), check status, or detach. Friendly — no long flags to remember. Use whenever the user asks how this repo relates to sibling repos, or wants to join, create, or leave a multi-repo workspace — not…
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.
t800-onboard
Для чата с новичками. Показывает, что настроено в Cursor (global + local), и что умеет отдел T-800.