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/seo-managergit 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.00017 | $0.02059 |
| Opus 5 | $0.00009 | $0.01030 |
| Sonnet 5 | $0.00003 | $0.00412 |
| Haiku 4.5 | $0.00002 | $0.00206 |
Grade A, and why
seo-manager 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fireauto-seo: SEO 종합 감사
현재 프로젝트의 SEO 상태를 7개 영역에 걸쳐 종합적으로 감사합니다. Next.js 프로젝트에 최적화되어 있으며, 실제 nomadfast, FireShipLanding, ditfinder 프로젝트 감사 경험을 바탕으로 합니다.
실행 절차
1단계: 프로젝트 구조 파악
먼저 프로젝트의 기본 구조를 파악합니다:
package.json을 읽어 프레임워크 확인 (Next.js 버전, 관련 패키지)next.config.*파일 확인src/app/또는app/디렉토리 구조 파악public/디렉토리 내 정적 파일 확인
2단계: 7개 영역 감사 수행
각 영역을 순차적으로 감사합니다. seo-auditor 에이전트를 호출하여 상세 감사를 수행합니다.
감사 영역 1: robots.txt 검증
점검 항목:
public/robots.txt또는app/robots.ts(동적 생성) 존재 여부User-agent규칙 적절성Disallow규칙으로 민감 경로 차단 여부 (admin, api, dashboard 등)Sitemap:지시자로 sitemap URL 참조 여부- 프로덕션 환경에서 전체 차단(
Disallow: /) 여부 점검
패턴 검색:
Glob: **/robots.{txt,ts,js}
Grep: "robots" in next.config.*
감사 영역 2: Sitemap 구조 분석
점검 항목:
public/sitemap.xml또는app/sitemap.ts(동적 생성) 존재 여부- sitemap index 사용 시 하위 sitemap 참조 유효성
- 모든 공개 라우트가 sitemap에 포함되어 있는지 비교
lastmod값의 정확성 (실제 콘텐츠 업데이트와 일치 여부)changefreq,priority설정 적절성- 다국어 사이트의 경우
xhtml:linkhreflang alternate 포함 여부
패턴 검색:
Glob: **/sitemap.{xml,ts,js}
Grep: "sitemap" in app/ directory
감사 영역 3: JSON-LD 구조화 데이터 감사
점검 항목:
@type적절성 검증:Organization/WebSite- 홈페이지Article/BlogPosting- 블로그/콘텐츠Product/Offer- 상품/가격FAQPage/Question- FAQ 섹션BreadcrumbList- 네비게이션Place/LocalBusiness- 장소 기반 페이지HowTo,Review,Event등 특수 타입
- 필수 속성 누락 검증 (각 @type별 required properties)
- Google Rich Results 호환성 (https://search.google.com/test/rich-results 기준)
- 동일 페이지 내 중복/충돌 JSON-LD 블록 감지
@id참조 일관성- 이미지, URL 등 속성값 유효성
패턴 검색:
Grep: "application/ld+json" in all tsx/jsx/ts/js files
Grep: "jsonLd" or "JsonLd" or "structured" in components
Grep: "@type" in lib/ or utils/ directories
감사 영역 4: 메타 태그 점검
점검 항목:
<title>태그: 존재, 길이(30-60자), 고유성<meta name="description">: 존재, 길이(120-160자), 고유성- Open Graph 태그:
og:title,og:description,og:image,og:url,og:type - Twitter Card 태그:
twitter:card,twitter:title,twitter:description,twitter:image - Canonical URL:
<link rel="canonical">존재 및 정확성 hreflang태그: 다국어 사이트 필수, 상호 참조 일관성viewport메타 태그- Next.js
metadata/generateMetadata사용 패턴 검증
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 · 230 lines · 17 tokens per session scan A 180a914e570c
seo-manager is a command published in the GitHub repository imgompanda/fireauto (140 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 2,059 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.