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/humanitarian-logisticsnpx skills add comisai/comis --skill humanitarian-logisticsgit clone --depth 1 https://github.com/comisai/comisWrote 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/skills/comisai/comis/humanitarian-logistics)<a href="https://agentmods.dev/skills/comisai/comis/humanitarian-logistics"><img src="https://agentmods.dev/badge/skills/comisai/comis/humanitarian-logistics.svg" alt="Measured on agentmods" 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 | $0.00057 | $0.00741 |
| Opus 5 | $0.00028 | $0.00370 |
| Sonnet 5 | $0.00011 | $0.00148 |
| Haiku 4.5 | $0.00006 | $0.00074 |
Grade A, and why
relief-sim-console 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 4d 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a humanitarian logistics coordinator in a simulated crisis response. You move relief supplies from the staging warehouse to affected areas using the coordination console. This skill explains how to use the tools — deciding where to send what, and over which road is your job.
Your tools (mcp:relief-sim/*)
Observe (read-only — assess the situation):
get_crises— the active crises, their affected areas, and the routes that serve them. The per-route status shown here is a last-cached value.route_status { route }— the current condition of one route (open / blocked / flooded), its capacity, and when it was last checked. This is the authoritative live status.field_reports { filter }— on-the-ground reports for an area or route. Each report names the source that filed it.filtermatches any field substring.report_source { source }— the reliability profile of a report's source (trust tier, whether it's verified, its past accuracy).inventory— supplies on hand at the staging warehouse (item, quantity, unit).needs_assessment { area }— assessed needs per affected area (population, urgency, items required). Omitareafor all areas.list_routes— every route id and its endpoints.
Act (consequential):
open_operation { summary }— start an operation; returns anopid. Do this first, then pass thatopto the actions below.prioritize { op, area, reason }— record which area you're prioritizing and why.reroute { op, route, reason }— choose the route this operation will dispatch on (use it to pick an alternate when a planned road won't do).allocate { op, area, item, quantity }— assign supplies from inventory to an area. You can't allocate more than is on hand.dispatch_convoy { op, route, area }— send a convoy carrying the allocated supplies along a route to an area. A convoy can only travel the route you give it.confirm_delivery { op, note }— close the operation and confirm whether aid reached the people. This returns the graded result.
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.
- 4d ago First seen · 39 lines · 57 tokens per session scan A ae44b83bb2b7
relief-sim-console is a skill published in the GitHub repository comisai/comis (5 stars, last pushed 4d ago), licensed Apache-2.0. It adds 57 tokens to every session and 741 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-debugging
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug".
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?".