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 skills/comisai/comis/wildfire-commandnpx skills add comisai/comis --skill wildfire-commandgit clone --depth 1 https://github.com/comisai/comisWhat 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.00060 | $0.00830 |
| Opus 5 | $0.00030 | $0.00415 |
| Sonnet 5 | $0.00012 | $0.00166 |
| Haiku 4.5 | $0.00006 | $0.00083 |
Grade A, and why
fire-sim-command 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the planning chief on a wildland fire. You run the incident using the incident-command tools. This skill explains how to use the tools — sizing up the fire and deciding what plan the conditions call for is your job.
Your tools (mcp:fire-sim/*)
Observe (read-only — size up the fire):
get_weather— wind, temperature, RH, and any forecast shift (a front, wind switch, or RH crash).fuel_moisture— the dominant fuel model, dead/live fuel moisture, and canopy/ladder-fuel continuity.terrain { zone }— slope, aspect, terrain features, and whether slope aligns with the wind for a zone (omitzonefor all zones).spread_forecast— modeled rate of spread, flame length, spotting distance, and which zones the head/flanks reach.resource_status— the crews, engines, dozers, and aircraft you have and their commit status.get_incident_map— the zones and their role (origin, head, flanks, values-at-risk like communities/structures).
Act (consequential):
open_incident { summary }— open the incident record; returns anincidentid. Do this first.set_tactic { incident, tactic, containment_line }— set your suppression tactic and where you anchor the containment line.assign_crew { incident, resource, zone, task }— put a crew/engine/dozer to work in a zone. The tool reports the safety posture; a ground crew sent into an unsafe (blow-up) zone is refused (not committed), so you can read the posture without endangering anyone — move them to a safe zone or use aircraft instead.order_air { incident, aircraft, zone }— order an air tanker or helicopter onto a zone.issue_evac { incident, zone, level }— order an evacuation for a zone with people/structures at risk.declare_contained { incident, note }— declare the fire contained and end the period. This returns the graded result.
How to run the incident
open_incidentto get anincidentid; pass thatincidentto the actions that follow.- Size up before you commit — pull weather, fuels, terrain, the spread forecast, the map, and your resource status with the observe tools.
set_tacticwith the plan the conditions call for and the containment line you anchor it on.assign_crew/order_airto put resources to work. Heed the safety posture the tool reports — it tells you whether a zone is safe for ground crews.issue_evacfor any zone where people or structures are in the fire's path.declare_containedwhen your plan is in place. This is graded.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 40 lines · 60 tokens per session scan A eee52bb8ecb5
fire-sim-command is a skill published in the GitHub repository comisai/comis (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 60 tokens to every session and 830 once invoked, about $0.0003 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-31.
Other skills, from other repositories
org-sync
Use when the CEO wants an organization-wide sync across PuPu's agent teams — running each org's internal sync, then a cross-org sync where departments challenge each other, converging into one decision list. Triggers: "跑一次 org sync", "全局同步", "组织盘点", "/org-sync", "各部门现在什么情况", "有什么要我拍板的".
release-feature-audit
Use when a new PuPu feature finishes implementation and needs its consistency audit before its ticket is marked done — "audit #123", "审计这个功能", "这个 feature 过一遍检查" — or when release-close-sprint roll-call finds a new feature that was never audited. Also covers standalone i18n checks ("漏翻了吗", "检查 i18n"), which used to be…
growth-analyst
Use when analyzing PuPu's open-source growth or health for the founder — GitHub traffic, downloads/installs, releases, community, or contributor activity — or when producing a growth report or weekly COO report. Repo is haoxiang-xu/PuPu. Triggers: "how is PuPu growing?", "are people installing PuPu?", "which release…
test-api
Use when running QA / regression tests against PuPu, when verifying a code change actually works in the running app, or when reading PuPu UI/state without screenshotting manually. Triggers on tasks like "test that PuPu still creates chats correctly", "verify the new model selector works end-to-end", "send a message…
gitnexus-impact-analysis
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?".
gitnexus-refactoring
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file".