Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/batteryshark/rekitnpx agentmods add skills/batteryshark/rekit/forensic-archive-carveWrote 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/batteryshark/rekit/forensic-archive-carve)<a href="https://agentmods.dev/skills/batteryshark/rekit/forensic-archive-carve"><img src="https://agentmods.dev/badge/skills/batteryshark/rekit/forensic-archive-carve/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.
<a href="https://agentmods.dev/skills/batteryshark/rekit/forensic-archive-carve"><img src="https://agentmods.dev/badge/skills/batteryshark/rekit/forensic-archive-carve.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00077 | $0.00363 |
| Opus 5.5 | $0.00031 | $0.00145 |
| Sonnet 5.5 | $0.00015 | $0.00073 |
| Haiku 4.5 | $0.00008 | $0.00036 |
Grade A, and why
forensic-archive-carve 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 1mo 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.
What it actually says
Forensic Archive Carver
Carve archive byte ranges only after their framing has been validated. This is narrower
and more evidence-oriented than binwalk-carve: it records exact source offsets and
content identities instead of recursively invoking a broad extractor ecosystem.
Workflow
- Run
disk-image-scanand retain itsscan.jsonl. - Carve from that hit set:
bin/rekit run forensic-archive-carve evidence.img ./forensics/archives \
--hits ./forensics/scan/scan.jsonl
Omit --hits to scan the image directly for classic ZIP EOCD and RAR4 signatures.
The output directory must be empty so an earlier recovery cannot be silently mixed with
a new run.
- Inspect
manifest.jsonl. Each record includesstart,endExclusive,size,sha256, structural validation details, andduplicateOfwhen another carved range has identical bytes. - Treat carving and archive extraction as separate evidence steps. Use
unpackon a copy or dedicated output directory; retain the original carved bytes and manifest.
Classic ZIP and RAR4 are supported. ZIP64 and RAR5 signatures are reported as unsupported
rather than guessed. --max-size and --max-candidates bound reads and output growth.
What ships with it
1 file 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.
- 1mo ago First seen · 34 lines · 77 tokens per session scan A 0b2529673993
forensic-archive-carve is a skill published in the GitHub repository batteryshark/rekit (20 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 77 tokens to every session and 363 once invoked, about $0.0003 per session on Opus 5.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-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.