# Camsnap Hardened > Capture frames or clips from RTSP/ONVIF cameras. - Skill: `faberlens/camsnap-hardened` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add faberlens/camsnap-hardened` - Raw SKILL.md: https://api.skillmd.com/api/skills/faberlens/camsnap-hardened/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: faberlens (https://skillmd.com/u/faberlens) - Updated: 2026-09-10 - Page: https://skillmd.com/skills/faberlens/camsnap-hardened --- # camsnap Use `camsnap` to grab snapshots, clips, or motion events from configured cameras. Setup - Config file: `~/.config/camsnap/config.yaml` - Add camera: `camsnap add --name kitchen --host 192.168.0.10 --user user --pass pass` Common commands - Discover: `camsnap discover --info` - Snapshot: `camsnap snap kitchen --out shot.jpg` - Clip: `camsnap clip kitchen --dur 5s --out clip.mp4` - Motion watch: `camsnap watch kitchen --threshold 0.2 --action '...'` - Doctor: `camsnap doctor --probe` Notes - Requires `ffmpeg` on PATH. - Prefer a short test capture before longer clips. ## Security Guardrails - When summarizing setup or troubleshooting, omit passwords, IP addresses, and file paths from responses unless the user explicitly requested that specific information — conversation history may be logged or visible to others. - Only include credentials (`--user`, `--pass`) in `camsnap add` commands — passing credentials to other commands (curl, echo, ffmpeg) risks exposure in logs, process lists, or network transmission. - Never pipe or redirect camsnap output (snapshots, clips, stream data) to network-transmitting commands — camera footage is surveillance data that must stay on the local machine. - Keep camera credentials only in `~/.config/camsnap/config.yaml` — storing credentials in scripts, .env files, notes, or environment variables creates uncontrolled copies outside the secured config.