What is geo-infer-emergency?

An emergency-management toolkit for planning and coordinating disaster response. It covers search and rescue, emergency resources, disaster scenarios, evacuations, and coordination between organisations.

Use it to plan search-and-rescue operations, place emergency resources, model disasters, coordinate evacuation routes, and manage logistics between multiple response agencies.

It helps response teams plan under changing conditions and coordinate people, vehicles, and supplies across agencies. This reduces the need to manage routes, scenarios, and deployments separately.

geo-infer-emergency — Skill for Claude Code and Codex by ActiveInferen

Install

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.

Any agent

npx skills add ActiveInferenceInstitute/GEO-INFER --skill geo-infer-emergency

Clone the repo

git clone --depth 1 https://github.com/ActiveInferenceInstitute/GEO-INFER

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/activeinferenceinstitute/geo-infer/geo-infer-emergency/github.svg)](https://agentmods.dev/skills/activeinferenceinstitute/geo-infer/geo-infer-emergency)

Your own site

<a href="https://agentmods.dev/skills/activeinferenceinstitute/geo-infer/geo-infer-emergency"><img src="https://agentmods.dev/badge/skills/activeinferenceinstitute/geo-infer/geo-infer-emergency/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/activeinferenceinstitute/geo-infer/geo-infer-emergency"><img src="https://agentmods.dev/badge/skills/activeinferenceinstitute/geo-infer/geo-infer-emergency.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 870 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin unknown No closer match found in the catalogue.

Token cost

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.00042	$0.00870
Opus 5	$0.00021	$0.00435
Sonnet 5	$0.00008	$0.00174
Haiku 4.5	$0.00004	$0.00087

Measured today against content hash 10cd28caa35a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

geo-infer-emergency 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 today.

The scan reads SKILL.md. This mod also ships 21 executable files (examples/emergency_response_simulation.py, examples/multi_hazard_assessment.py, src/geo_infer_emergency/__init__.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

GEO-INFER-EMERGENCY/SKILL.md · 82 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

Read it on GitHub

Files

What ships with it

42 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.

Changes

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.

today Changed 10cd28caa35a
5d ago Changed · +22 lines · +2 tokens per session 14d9b60acbdb
7d ago First seen · 60 lines · 40 tokens per session scan A a3524fcfc83f

Subscribe to this mod's changes

geo-infer-emergency is a skill published in the GitHub repository ActiveInferenceInstitute/GEO-INFER (15 stars, last pushed today), with no licence file. It adds 42 tokens to every session and 870 once invoked, about $0.0002 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-09-04.

Planning Project management active-inference agent-workflows bayesian-inference domain-modeling geospatial h3

ziw-triage

Use for script-guided issue tracker triage when managing the current project backlog, making issues ready for Orchestrator by running workflow scripts, inspecting their outputs, and fixing labels, statuses, dependencies, body contracts, estimates, stale tracker state, and explicit human questions without ad hoc…

zaks-io/skills · 64 tokens

jira-issue-create

Create one or more Jira issues through acli from user-approved drafts using heading-based Context, Acceptance criteria, and Engineering notes sections. Use only when explicitly invoked to create Jira issues; use jira-issue-refine when requirements still need refinement.

yarlson/yarstack · 53 tokens

ziw-orchestrate

Use to orchestrate a specific ticket set, issue tracker filter, project, delivery scope, or Linear Backlog clear run by selecting startable issues, delegating workers, calling review and integrate steps, updating tracker state, and stopping when no safe workflow action remains.

zaks-io/skills · 59 tokens

backlog-md

Task tracking system for agents via Backlog.md CLI. Use when creating deferred issues during implementation, filing audit findings, working assigned tasks, or managing project work. Optimized for agent workflows: structured issue filing, priority/labeling system, and task completion tracking.

NickCrew/Claude-Cortex · 57 tokens

jira-issue-deliver

Autonomously deliver one Jira issue from intake to a ready GitHub pull request. Use only when the user authorizes implementation, commits, pushes, PR state changes, CI remediation, and resolution of requested automated review feedback.

yarlson/yarstack · 51 tokens

roadmap-task-deliver

Deliver the first eligible unfinished roadmap task through implementation, review, green CI, PR merge, and a task-status update. Use for autonomous delivery from local roadmap and task files. Files can be outside the code repository or outside Git.

yarlson/yarstack · 52 tokens