Borrowing it
Nothing to install: this file belongs to stevengonsalvez/agents-in-a-box. 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/stevengonsalvez/agents-in-a-box/main/.claude/skills/tmux-verify/SKILL.mdgit clone --depth 1 https://github.com/stevengonsalvez/agents-in-a-boxWrote 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/stevengonsalvez/agents-in-a-box/tmux-verify)<a href="https://agentmods.dev/skills/stevengonsalvez/agents-in-a-box/tmux-verify"><img src="https://agentmods.dev/badge/skills/stevengonsalvez/agents-in-a-box/tmux-verify/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/stevengonsalvez/agents-in-a-box/tmux-verify"><img src="https://agentmods.dev/badge/skills/stevengonsalvez/agents-in-a-box/tmux-verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00231 | $0.02262 |
| Opus 5 | $0.00115 | $0.01131 |
| Sonnet 5 | $0.00046 | $0.00452 |
| Haiku 4.5 | $0.00023 | $0.00226 |
Grade A, and why
tmux-verify 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 11d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tmux-verify
Overview
tmux-verify is the OUTER acceptance harness: it proves a TUI feature is actually done as a user would experience it. It does NOT write the automated test (that is tmux-ui-tripwire) and does NOT reimplement media tooling (that is /media-processing). It orchestrates both plus a live explainer into one repeatable contract.
Use it two ways:
- As a contract — a goal/plan says "validate per
/tmux-verify" and inherits all 6 gates. - As a runner — execute the gates for a feature end-to-end until green.
The non-negotiable principle: read the frame, don't blank-check. A passing screen is one whose pixels/text say the correct thing for that journey — not merely that something rendered.
The 6 gates
┌──────────────────────────────────────────────┐
G1 automated ───────▶ │ tmux-ui-tripwire: comprehensive, VT100-true, │
(ref skill) │ passes in the real TUI, non-flaky ×3 │
└──────────────────────────────────────────────┘
G2+G3 visual ┌──────────────────────────────────────────────┐
(THIS SKILL OWNS) ───▶ │ per journey: .tape ─▶ vhs ─▶ gif+mp4 │
│ ─▶ ffmpeg frames ─▶ READ + assert│
│ one recording per journey │
└──────────────────────────────────────────────┘
G4 fix-loop ───────▶ acceptance(cargo test) + tripwire green; unbounded
until green or a genuine hard blocker (then log + go on)
G5 explainer ───────▶ /explain-to-me ─▶ /here-now (stable slug, republish
each phase: progress · test/clippy/tripwire output ·
commit log · embedded per-journey GIFs)
G6 final ───────▶ HTML solid (fetch URL: links resolve, GIFs load,
no empty sections) ─▶ HUMAN validates → done
Gate-by-gate playbook
What ships with it
6 files 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.
- 11d ago First seen · 99 lines · 231 tokens per session scan A b8b2bffd4763
tmux-verify is a skill published in the GitHub repository stevengonsalvez/agents-in-a-box (23 stars, last pushed today), licensed MIT. It adds 231 tokens to every session and 2,262 once invoked, about $0.0012 per session on Opus 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
verification-before-completion
A workflow rule for checking command results before saying that coding work is finished, fixed, or tested. It requires fresh evidence such as test output, linter results, or a successful build.
test-driven-development
A test-driven development (TDD) workflow: write a test first, confirm that it fails, add the smallest implementation, and then clean up the code.
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.
web3-testing
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
data-quality-frameworks
Implement data quality validation with Great Expectations, dbt tests, and data contracts. Use when building data quality pipelines, implementing validation rules, or establishing data contracts.