Individual skill
casefile
Use when tracking security investigations, bug bounty findings, CTF leads, audit evidence, exploit chains, dead ends, or reports in the Casefile ledger through Codex.
plugins/x4cc3/casefile/skills/casefile/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,530
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,843 bytes
Read excerpt
# Casefile
Use Casefile to maintain durable security investigation state across Codex turns. Prefer the MCP tools from the `casefile` server when they are available.
## Workflow
1. Check existing cases before opening a new one with `casefile_list` or `casefile_search`.
2. Open new leads with `casefile_add` as `hypothesis` or `investigating`.
3. Promote cases with `casefile_update` only after materially new evidence, proof, impact, blockers, remediation, or status changes.
4. Mark `confirmed` only when evidence and a PoC or repro are recorded.
5. Use `casefile_link` and `casefile_unlink` for exploit chains. Do not edit linked case IDs directly.
6. Use `casefile_report` only for confirmed or already reported cases.
7. Use `killed` for disproven, duplicate, or dead-end leads, and include evidence, blockers, next step, or assumptions explaining why.
