Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/putervision/spc/video-ingestnpx skills add putervision/spc --skill video-ingestgit clone --depth 1 https://github.com/putervision/spcWrote 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/putervision/spc/video-ingest)<a href="https://agentmods.dev/skills/putervision/spc/video-ingest"><img src="https://agentmods.dev/badge/skills/putervision/spc/video-ingest.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 | $0.00038 | $0.00877 |
| Opus 5 | $0.00019 | $0.00439 |
| Sonnet 5 | $0.00008 | $0.00175 |
| Haiku 4.5 | $0.00004 | $0.00088 |
Grade A, and why
video-ingest 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 5d 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.
This is a copy
100% identical to video-ingest — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Video Frame Digesting & Temporal Memory Skill (video-ingest)
This skill provides step-by-step guidance, best practices, and operational patterns for digesting WebM, MP4, and GIF video recordings using @putervision/vision-memory-mcp.
1. When to Use Video Ingestion
Use video ingestion whenever you encounter:
- E2E Playwright / Cypress / Selenium Test Artifacts: Recorded
.webmscreenchunks or.mp4test run videos. - Bug Reproduction Videos: User-uploaded screen recordings demonstrating UI glitches or crashes.
- UI Walkthrough Recordings: Demonstrations of complex multi-step user workflows.
- Visual Regression Diagnostics: Comparing a passing baseline video run against a failing test run.
2. Ingestion Strategies & Parameter Tuning
| Scenario | Recommended Parameters | Why |
|---|---|---|
| Action Event Timestamps (Highest Precision) | action_timestamps: [1.2, 3.5, 7.0] |
Samples keyframes at exact interaction timestamps (clicks, types, navigation events) from test runners or state-memory logs. |
| Dynamic UI / Animations | scene_threshold: 0.3, fps: 1 |
Combines scene-change detection (gt(scene,0.3)) with 1 fps background sampling to capture major screen transitions without frame bloat. |
| High-Speed Test Runs | fps: 2 or fps: 5 |
Increases frame rate sampling for rapidly switching UI test steps. |
| Long Screen Recordings | fps: 0.5, scene_threshold: 0.4 |
Lowers sampling rate to conserve storage while extracting unique keyframe states. |
3. Mandatory Dual-MCP Evidence Workflow
When diagnosing bugs or linking test runs to task nodes:
- Ingest Video: Call
manage_video(action: "ingest") with file path and action timestamps. - Extract Evidence Payload: Read the returned
evidence_payloadcontainingsource_video_id,frame_range, andtimestamps_ms. - Build Evidence Pack: Call
create_evidence_packlinkingkeyframe_state_idswithstate-memory-mcptask or blocker node IDs. - Compare Trajectories (On Failure): Call
compare_states(video_a_id: "...", video_b_id: "...")to pinpoint exact frame divergence points.
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.
- 5d ago First seen · 69 lines · 38 tokens per session scan A a4ba4c1c9275
video-ingest is a skill published in the GitHub repository putervision/spc (39 stars, last pushed 14d ago), licensed MIT. It adds 38 tokens to every session and 877 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to video-ingest, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
analyzing-packed-malware-with-upx-unpacker
Identifies and unpacks UPX-packed malware samples, including binaries with modified UPX magic bytes or headers that block automated decompression, to recover the original executable for static analysis. Use when a sample shows high entropy, minimal imports, or only LoadLibrary/GetProcAddress in its import table, or…
analyzing-malicious-pdf-with-peepdf
Perform static analysis of malicious PDF documents using peepdf, pdfid, and pdf-parser to extract embedded JavaScript, shellcode, and suspicious objects. Use when triaging a suspicious PDF attachment from a phishing email, analyzing a PDF-based exploit document, or building detection signatures for weaponized PDF…
analyzing-android-malware-with-apktool
Perform static analysis of Android APK malware using apktool for resource decompilation, jadx for Java source recovery, and androguard for manifest inspection, dangerous permission-combination detection, and identification of obfuscated code, dynamic code loading, and reflection-based API calls. Use to statically…
implementing-semgrep-for-custom-sast-rules
Write custom Semgrep SAST rules in YAML to detect application-specific vulnerabilities, enforce coding standards, and integrate into CI/CD pipelines.
cli-analysis
Run the pyscn command-line tool for Python code quality analysis - CI/CD quality gates, HTML/JSON/CSV reports, full analysis runs, and project configuration. Use when user wants a CI check, a shareable report file, or to configure pyscn for a project.
health-check
Get an overall Python code quality health score using pyscn. Use when user asks how healthy or good the code is, wants a quality overview, a grade, a summary of technical debt, or a before/after quality comparison.