Borrowing it
Nothing to install: this file belongs to chayuto/ws-ESP32-S3-CAM. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/chayuto/ws-ESP32-S3-CAM/main/.claude/commands/extract-session.mdgit clone --depth 1 https://github.com/chayuto/ws-ESP32-S3-CAMWrote 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/commands/chayuto/ws-esp32-s3-cam/extract-session)<a href="https://agentmods.dev/commands/chayuto/ws-esp32-s3-cam/extract-session"><img src="https://agentmods.dev/badge/commands/chayuto/ws-esp32-s3-cam/extract-session.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.1 | $0.00000 | $0.00610 |
| Opus 5 | $0.00000 | $0.00305 |
| Sonnet 5 | $0.00000 | $0.00122 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
extract-session 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 8d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Close out a capture session
One-shot mirror of the deployed device + audit run for an overnight capture. Idempotent — safe to rerun partway through the night, or to refresh a session where the WAVs are already downloaded but device logs keep growing.
Usage: /extract-session <session_dir> [host]
<session_dir>— e.g.logs/night-20260419(will be created if missing).[host]— defaults tohttp://192.168.1.100.
What it does
Executes projects/cry-detect-01/tools/extract_session.sh, which:
- Kills the running bash monitor if one was started from the same
session dir. (Looks up
<session_dir>/monitor.shinpgrep.) - Mirrors
/sdcard/events/→<session_dir>/wavs/*.wav+<session_dir>/triggers.jsonl. Existing files are skipped. - Mirrors
/sdcard/root logs (infer-*.jsonl,cry-*.log,infer-boot.jsonl,CRY-0000.LOG) →<session_dir>/device-logs/. These are re-downloaded every run because the device keeps appending while online. - Runs the audit pipeline via
tools/audit_pipeline.sh— producesmanifest.csv/segments.csv/yamnet_files.csv/yamnet_segments.csv/specgrams/*.png. - Writes a
README.mdstub if none exists yet. Fill it in before archival (see the taxonomy rules indocs/research/file-management-strategy-20260419.md).
Conventions
- Session directory name:
logs/night-YYYYMMDD, dated by the start of the night (the evening the deployment began). - Device is assumed reachable at
http://192.168.1.100; override if running on a different LAN. - Never edits files already present. Won't
rmWAVs. - If the device is offline at the time the command runs, the mirror step short-circuits gracefully and the audit runs on whatever is already on disk.
When to invoke
- End of every overnight capture, first thing in the morning.
- After any accidental monitor death (data since last download will still come through because infer-*.jsonl is day-bucketed and append-only on the device).
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.
- 8d ago First seen · 59 lines · 0 tokens per session scan A e0ef3f096e56
extract-session is a command published in the GitHub repository chayuto/ws-ESP32-S3-CAM (5 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 610 tokens. 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 commands, from other repositories
review-firmware
Run embedded firmware code review (memory safety, ISR, RTOS, C/C++ UB).
power-budget
Calculate power budget for the current embedded project.
bom
Generate or analyze Bill of Materials from KiCad project.
debug
Start GDB debug session with OpenOCD or probe-rs.
flash
Build and flash firmware to target device (ESP-IDF or PlatformIO).
ruview-app
Run a RuView sensing application — presence, vitals, pose, sleep, environment mapping, MAT, point cloud, or a novel RF app.