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/designergit 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.00021 | $0.03231 |
| Opus 5 | $0.00010 | $0.01615 |
| Sonnet 5 | $0.00004 | $0.00646 |
| Haiku 4.5 | $0.00002 | $0.00323 |
Grade A, and why
designer 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 yesterday.
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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fireauto-ui: DaisyUI v5 UI 툴킷
DaisyUI v5 기반으로 UI를 구축하거나, shadcn/ui에서 DaisyUI로 마이그레이션하거나, 테마를 설정하는 통합 명령어입니다.
사용법
사용자 메시지에서 모드를 파악하세요:
- migrate 키워드 또는 "마이그레이션", "변환", "전환" -> 마이그레이션 모드
- build 키워드 또는 "만들어", "구축", "생성" -> 빌드 모드
- theme 키워드 또는 "테마", "색상", "컬러" -> 테마 모드
모드 1: migrate (shadcn/ui -> DaisyUI 마이그레이션)
단계별 절차
- 스캔:
@/components/ui/에서 import하는 파일들을 Grep으로 검색 - 매핑: 각 shadcn 컴포넌트를 DaisyUI 클래스로 변환
- 교체: import 제거, JSX에 DaisyUI 클래스 적용
- 정리: 미사용 shadcn 컴포넌트 파일 삭제
컴포넌트 매핑 테이블
| shadcn/ui | DaisyUI v5 | 비고 |
|---|---|---|
<Button> |
<button className="btn"> |
variant 아래 참조 |
<Button variant="default"> |
btn btn-primary |
|
<Button variant="destructive"> |
btn btn-error |
|
<Button variant="outline"> |
btn btn-outline |
|
<Button variant="secondary"> |
btn btn-secondary |
|
<Button variant="ghost"> |
btn btn-ghost |
|
<Button variant="link"> |
btn btn-link |
|
<Button size="sm"> |
btn btn-sm |
|
<Button size="lg"> |
btn btn-lg |
|
<Card> |
<div className="card bg-base-100 shadow-xl"> |
|
<CardHeader> |
<div className="card-body"> (상단부) |
|
<CardTitle> |
<h2 className="card-title"> |
|
<CardContent> |
<div className="card-body"> |
|
<CardFooter> |
<div className="card-actions justify-end"> |
|
<Badge> |
<span className="badge"> |
|
<Badge variant="destructive"> |
badge badge-error |
|
<Badge variant="outline"> |
badge badge-outline |
|
<Badge variant="secondary"> |
badge badge-secondary |
|
<Dialog> |
<dialog className="modal"> |
DaisyUI modal 패턴 사용 |
<DialogTrigger> |
<button onclick="modal_id.showModal()"> |
|
<DialogContent> |
<div className="modal-box"> |
|
<DialogHeader> |
제거, modal-box 내부에 직접 배치 | |
<DialogTitle> |
<h3 className="font-bold text-lg"> |
|
<DialogDescription> |
<p className="py-4"> |
|
<DialogFooter> |
<div className="modal-action"> |
|
<Input> |
<input className="input input-bordered"> |
|
<Textarea> |
<textarea className="textarea textarea-bordered"> |
|
<Select> |
<select className="select select-bordered"> |
|
<Checkbox> |
<input type="checkbox" className="checkbox"> |
|
<Switch> |
<input type="checkbox" className="toggle"> |
|
<Tabs> |
<div role="tablist" className="tabs tabs-bordered"> |
|
<TabsTrigger> |
<a role="tab" className="tab"> |
|
<TabsContent> |
일반 div, tab 활성화 상태로 제어 | |
<Accordion> |
DaisyUI collapse 또는 details/summary | |
<Alert> |
<div role="alert" className="alert"> |
|
<Avatar> |
<div className="avatar"><div className="w-10 rounded-full"> |
|
<DropdownMenu> |
<div className="dropdown"> |
|
<Tooltip> |
<div className="tooltip" data-tip="..."> |
|
<Progress> |
<progress className="progress"> |
|
<Skeleton> |
<div className="skeleton"> |
|
<Table> |
<table className="table"> |
|
<Separator> |
<div className="divider"> |
|
<Sheet> |
<div className="drawer"> |
|
<Popover> |
<div className="dropdown"> |
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.
- yesterday First seen · 270 lines · 21 tokens per session scan A f6b74b691efd
designer is a command published in the GitHub repository imgompanda/fireauto (140 stars, last pushed 4mo ago), licensed MIT. It adds 21 tokens to every session and 3,231 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.