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/imgompanda/fireautoWrote 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/imgompanda/fireauto/next)<a href="https://agentmods.dev/commands/imgompanda/fireauto/next"><img src="https://agentmods.dev/badge/commands/imgompanda/fireauto/next/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/imgompanda/fireauto/next"><img src="https://agentmods.dev/badge/commands/imgompanda/fireauto/next.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.00791 |
| Opus 5.5 | $0.00012 | $0.00316 |
| Sonnet 5.5 | $0.00006 | $0.00158 |
| Haiku 4.5 | $0.00003 | $0.00079 |
Grade A, and why
next 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 1mo 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
fireauto-next: 다음 태스크 시작
다음에 해야 할 태스크를 자동으로 찾아서, 관련 지식과 함께 보여줘요. 바로 시작할 수 있도록 컨텍스트를 미리 준비해줘요.
모든 출력은 **한국어(토스체)**로 작성하고, 기술 용어는 영어를 병기해요.
Step 1: 다음 태스크 조회
project-next MCP 도구를 호출해서 다음에 해야 할 태스크를 조회하세요.
Step 2: 관련 지식 검색
태스크를 찾았으면, memory-search MCP 도구로 관련 지식을 자동 검색하세요.
검색 키워드는 태스크 제목과 설명에서 추출해요:
- 기술 키워드 (React, API, Auth 등)
- 도메인 키워드 (결제, 인증, 대시보드 등)
- 관련 파일명이나 모듈명
Step 3: 태스크 안내
조회 결과를 아래 형식으로 보여주세요:
🎯 다음 태스크
📋 {태스크명}
프로젝트: {프로젝트명}
마일스톤: {마일스톤명}
설명: {태스크 설명}
💡 관련 지식
• {memory-search 결과 1}
• {memory-search 결과 2}
(관련 지식이 없으면 이 섹션 생략)
시작할까요? (y/n)
활성 태스크가 없으면:
✅ 모든 태스크를 완료했어요! 대단해요!
새 프로젝트를 만들려면 /project new 를 실행해 보세요.
🌐 대시보드: http://localhost:37888
Step 4: 태스크 실행
사용자가 "시작할게", "y", "네", "ㅇ" 등 긍정 응답을 하면:
- 태스크의 상태를
project-task-updateMCP 도구로in_progress로 변경해요 - 태스크 설명과 관련 지식을 바탕으로 바로 작업을 시작해요
- 코드 생성, 파일 수정 등 실제 개발 작업을 수행해요
사용자가 "아니", "n", "다른 거", "스킵" 등 부정 응답을 하면:
이 태스크를 건너뛸게요. 다른 태스크를 보려면 다시 /next 를 실행해 주세요.
Step 5: 태스크 완료 처리
작업이 끝나면:
project-task-updateMCP 도구로 태스크 상태를completed로 변경해요- 작업 중 발견한 중요한 지식이 있으면
memory-saveMCP 도구로 저장해요 - 완료 메시지를 보여주세요:
✅ "{태스크명}" 완료!
📊 프로젝트 진행률: ██████░░░░ {진행률}%
📋 다음 태스크가 궁금하면 /next 를 다시 실행해 보세요.
톤 & 스타일 가이드
- 언어: 한국어 (기술 용어는 영어 병기)
- 문체: 토스체 — 친근하고 명확하게
- 이모지: 섹션 구분용으로 최소한 사용
- 행동 유도: 항상 다음 액션을 제안해요
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.
- 1mo ago First seen · 107 lines · 30 tokens per session scan A 03896d9d36d9
next is a command published in the GitHub repository imgompanda/fireauto (140 stars, last pushed 6mo ago), licensed MIT. It adds 30 tokens to every session and 791 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-08-30.
Other commands, from other repositories
flow
Conductor - an idea or change request, a spec or task id, a tracker issue, a branch or path, a bug report, a how or why question, something slow, a behaviour-keeping cleanup, a design fork, or "what next"; --auto drives a ready spec unattended (--tick for one hop) and ends with a PILOTVERDICT line; --until=merge…
tracker-sync
Project a flow spec to a tracker (Linear/GitHub/GitLab/Jira) and reconcile body/status/comments two-way — projection, not coordination. NOT plan-sync (/flow-next:sync).
audit
Audit .flow/memory/ entries against the current codebase — Keep / Update / Consolidate / Replace / Delete / Harden per entry.
make-pr
Render a cognitive-aid PR body from flow-next state and open via gh.
features
Seed or maintain the committed user-POV feature map at .flow/features/.
land
Resolve and squash merge one named, currently authorized pull request.