Borrowing it
Nothing to install: this file belongs to jleechanorg/agent-orchestrator-ts. 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/jleechanorg/agent-orchestrator-ts/main/.claude/commands/pr-media.mdgit clone --depth 1 https://github.com/jleechanorg/agent-orchestrator-tsWrote 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/jleechanorg/agent-orchestrator-ts/pr-media)<a href="https://agentmods.dev/commands/jleechanorg/agent-orchestrator-ts/pr-media"><img src="https://agentmods.dev/badge/commands/jleechanorg/agent-orchestrator-ts/pr-media/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/commands/jleechanorg/agent-orchestrator-ts/pr-media"><img src="https://agentmods.dev/badge/commands/jleechanorg/agent-orchestrator-ts/pr-media.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.00000 | $0.01001 |
| Opus 5.5 | $0.00000 | $0.00400 |
| Sonnet 5.5 | $0.00000 | $0.00200 |
| Haiku 4.5 | $0.00000 | $0.00100 |
Grade A, and why
pr-media 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 9d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pr-media — Capture and attach terminal media to PRs
Run the actual capture script, not prose guidance.
# Capture screenshot of current tmux pane + upload to Gist + post to PR
bash scripts/pr-media.sh
# Dry-run (capture + upload, skip PR comment)
bash scripts/pr-media.sh --test
# With options
bash scripts/pr-media.sh --type screenshot --pr 281 --caption "AO worker showing test pass"
bash scripts/pr-media.sh --type gif # 5-second clip → GIF (requires ffmpeg + gifski)
bash scripts/pr-media.sh --type video # 10-second recording (requires ffmpeg)
The script (scripts/pr-media.sh) implements the Terminal media requirement of Evidence Bundle v2 (CLAUDE.md).
Philosophy (Cursor-style evidence)
Cursor's cloud agents produce artifacts (videos, screenshots, and logs) and merge-ready PRs with artifacts so reviewers can validate work without trusting prose alone. The /pr-media command automates the capture step so agents attach real terminal proof to every PR.
Evidence Bundle v2 requires (CLAUDE.md Evidence Gate strong proof):
- Terminal media: screenshot or video URL + caption mentioning
tmuxorterminal - Caption outside the label line — the caption must describe what the media shows, not just repeat the label
Usage
/pr-media [--type screenshot|video|gif] [--pr N] [--caption "text"]
Arguments
| Flag | Default | Description |
|---|---|---|
--type |
screenshot |
Media type: screenshot, video, or gif |
--pr |
auto-detect | PR number; auto-detected from current branch |
--caption |
auto | Caption text; auto-generates if omitted |
Examples
/pr-media
/pr-media --type screenshot
/pr-media --type video --caption "AO worker session showing PR merge confirmation"
/pr-media --type gif
/pr-media --pr 281
Workflow
- Capture —
screencapture(screenshot) orffmpeg(video/gif) captures the tmux pane - Upload — file is uploaded to GitHub Gist via
gh gist create(authenticated, secret by default) - Attach — GitHub comment is posted on the target PR with the media URL in markdown
- Output — prints the markdown snippet to stdout for copy-paste into PR body
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.
- 9d ago First seen · 105 lines · 0 tokens per session scan A ac3609948ea4
pr-media is a command published in the GitHub repository jleechanorg/agent-orchestrator-ts (8 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,001 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-10-02.
Other commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.