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/HelixDevelopment/codenpx agentmods add skills/helixdevelopment/code/media-validatorWrote 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/helixdevelopment/code/media-validator)<a href="https://agentmods.dev/skills/helixdevelopment/code/media-validator"><img src="https://agentmods.dev/badge/skills/helixdevelopment/code/media-validator/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/helixdevelopment/code/media-validator"><img src="https://agentmods.dev/badge/skills/helixdevelopment/code/media-validator.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.00086 | $0.00623 |
| Opus 5.5 | $0.00034 | $0.00249 |
| Sonnet 5.5 | $0.00017 | $0.00125 |
| Haiku 4.5 | $0.00009 | $0.00062 |
Grade A, and why
media-validator 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 2d 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
Media Validator Skill
Purpose
Validates media files (MP4, PNG, TXT) by running OCR, metadata checks, and pattern matching against expected content. Returns PASS/FAIL with evidence.
Usage
bash skills/media-validator/media-validator.sh <file> [expected-pattern...]
Inputs
file— path to an MP4, PNG, or TXT fileexpected-pattern— one or more grep/extended regex patterns expected in the extracted text
Outputs
- stdout:
PASS: <description> [evidence: <path>]orFAIL: <reason> - Evidence file at
qa-results/media-validator/<timestamp>-<basename>/ - Exit 0 on PASS, 1 on FAIL, 2 on SKIP
Dependencies
tesseract(optional — for OCR on images/video frames)ffmpeg(optional — for frame extraction from MP4)ffprobe(optional — for video metadata)file(for MIME detection)
Cross-references
- constitution/Constitution.md §11.4.107 (liveness evidence)
- constitution/Constitution.md §11.4.117 (CV/OCR pixel oracle)
- constitution/Constitution.md §11.4.137 (subtitle correctness)
- constitution/Constitution.md §11.4.69 (sink-side evidence taxonomy)
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.
- 2d ago Changed · +1 lines · +65 tokens per session 7c80fffbd640
- 1mo ago First seen · 45 lines · 21 tokens per session scan A 85a067b5473c
media-validator is a skill published in the GitHub repository HelixDevelopment/code (2 stars, last pushed 2d ago), licensed MIT. It adds 86 tokens to every session and 623 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-31.
Other skills, from other repositories
pod-e2e
ONLY for developing Kiro Crew itself -- if the project you are working on is anything else, ignore this skill: it drives Kiro Crew's own pod tooling, which does not exist in another repository. Boots a Kiro Crew feature worktree's full stack as an ISOLATED throwaway pod and proves it boots, authenticates and renders…
relay-80-100-workflow
Use when writing agent-relay workflows that must fully validate features end-to-end before merging. Covers the 80-to-100 pattern - going beyond "code compiles" to "feature works, tested E2E locally." Includes repair-before-failure validation gates, review-depth fresh-eyes review/fix loops with test hardening, PGlite…
browser-testing-with-screenshots
Use when testing web applications with visual verification - automates Chrome browser interactions, element selection, and screenshot capture for confirming UI functionality.
browser-qa
Testing web apps through a real browser: reconnaissance before acting, selector discovery, state capture, console errors and screenshot evidence. Use on a web surface end to end, or to reproduce a front-end bug.
rn-testing
This skill should be used when the user asks to "write a Maestro test", "create E2E flows", "add testIDs", "run UI tests", "run E2E tests", "verify a feature works", "test my screen", "set up maestro-runner", "mock network requests", "inspect store state", "write test assertions", or needs guidance on test timing…
capturing-proof
This skill should be used when the user asks to "capture proof", "record a demo of this feature", "make a video showing it works", "record the flow for the PR", "generate a PR body", "capture screenshots for the PR", "proof-capture", or when a verified feature needs PR-ready proof artifacts (video + numbered…