# Joint Explosive Ordnance Disposal Render Safe And Site Exploitation Cell

> Coordinate EOD render-safe actions, technical exploitation, and site-control recommendations for U.S. warfighters. Use when unexploded ordnance, improvised threats, or captured munitions require both neutralization and evidence or intelligence recovery.

- Skill: `zwright8/joint-explosive-ordnance-disposal-render-safe-and-site-explo` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add zwright8/joint-explosive-ordnance-disposal-render-safe-and-site-explo`
- Raw SKILL.md: https://api.skillmd.com/api/skills/zwright8/joint-explosive-ordnance-disposal-render-safe-and-site-explo/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: zwright8 (https://skillmd.com/u/zwright8)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/zwright8/joint-explosive-ordnance-disposal-render-safe-and-site-explo

---


# Joint Explosive Ordnance Disposal Render Safe And Site Exploitation Cell

## Mission Scope

- Treat this skill as planning and decision support for U.S. warfighter render-safe, technical exploitation, and protected-site exploitation decisions.
- Confirm threat type, site security, evidence handling rules, blast standoff, exploitation priority, and decision deadlines before recommending action.
- Keep outputs unclassified by default unless explicit handling guidance is provided.

## Workflow

1. Frame the mission problem with ordnance identification, initiator state, site access, forensic value, and civilian or friendly-force exposure.
2. Build one recommended COA and at least two alternatives with explicit tradeoffs in safety, intelligence gain, tempo, and escalation risk.
3. Identify branch triggers for evacuation, remote action, evidence freeze, demolition, and transfer to follow-on exploitation teams.
4. Bind each critical recommendation to concrete external tools, protocol stacks, and packet templates.
5. Publish commander and EOD leader decision prompts plus a staff tracker with owner, suspense, confidence, and revalidation trigger.

## Required Output Format

1. Situation snapshot and key changes.
2. Recommended COA and rationale.
3. Alternative COAs with trigger conditions.
4. Decision points and escalation gates.
5. Staff tasks by owner and suspense.
6. Tool invocation packets with protocol bindings.

## Domain Products

Primary products: render-safe action ladder, site exploitation evidence matrix, and standoff or cordon decision board.

## Domain Toolchain Defaults

- Primary: `tool_suite_id=ts-joint-eod-render-safe-site-exploitation-v1` with `protocol_stack_id=ps-joint-eod-render-safe-site-exploitation-stack-v1`.
- Alternate: select a mission-adjacent EOD, forensics, or force-protection suite or stack from `../_shared/references/warfighter-external-tool-and-protocol-catalog.md` and explain tradeoffs.
- Degraded: manual cordon board with voice-verified standoff checks, paper evidence log, and demolition hold until authority is confirmed.

## Domain Packet Defaults

- Default packet ID: `DPL-EOD-RENDER-SAFE-SSE-001`.
- Preferred `toolchain_id=TC-EOD-136` and `toolchain_profile_id=eod-render-safe-site-exploitation-v1`.
- If no packet matches mission conditions, create a provisional packet using the shared schema and assign a validation owner.

## External Tool Stack and Protocols

- Preferred external toolsets for this domain: render-safe planner, ordnance fingerprint ledger, blast standoff board, and site exploitation evidence workbench.
- Preferred protocol profiles for coordination and machine exchange: `USMTF`, `NIEM`, `STIX/TAXII`, signed evidence manifests, `API/JSON`, and `OGC`.
- Use `../_shared/references/warfighter-external-tool-and-protocol-catalog.md`, `../_shared/references/domain-tool-packet-library.md`, and `../_shared/references/tool-protocol-playbooks.md`.
- Include provenance metadata: source system, UTC refresh timestamp, confidence, and known gaps.

## Tool Invocation Contract

For each critical tool recommendation include objective, required inputs, query or action template, expected output schema, protocol or transport, and fallback path.

## Mission Tool Authority Gates

- Apply authority and escalation requirements in `../_shared/references/human-agent-command-escalation-matrix.md` and `../_shared/references/warfighter-tool-authority-gates.md`.
- Include `authority_tier`, `decision_impact_level`, `approval_role`, and `audit_record_id` for posture-changing actions.
- If ordnance identification, blast-safety data, or evidence-custody authority is uncertain, downgrade to advisory-only and request human command review.

## Interoperability Validation Checklist

- Run `../_shared/references/mission-assurance-checklist.md` and `../_shared/references/us-joint-protocol-assurance-drill.md` before release.
- Validate protocol conformance, UTC freshness, confidence declaration, and branch-trigger clarity.
- If checks fail, provide a degraded-mode branch with explicit operational risk.

## Guardrails

- Separate verified facts, assessed judgments, assumptions, and unknowns.
- Flag public-safety risk, exploitation contamination, misidentification risk, and unconfirmed fuzing state before recommending action.
- Do not fabricate threat identity, blast clearance, or evidence chain-of-custody integrity.