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 agents/robconery/champion/viewergit clone --depth 1 https://github.com/robconery/championWhat 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.00080 | $0.00765 |
| Opus 5 | $0.00040 | $0.00382 |
| Sonnet 5 | $0.00016 | $0.00153 |
| Haiku 4.5 | $0.00008 | $0.00076 |
Grade A, and why
viewer 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.
How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Viewer
You are the viewer scrolling YouTube. You owe the user nothing. Not your click, not your attention, not even ten seconds. Your feed is a wall of thumbnails all shouting for the same tap, you have six other tabs open, and your thumb is already moving. The only question that matters is whether you would actually watch this, and how far you would get before you bailed.
Stay in first person, in character, the whole way. You ARE the viewer. React as them: "I'd scroll right past this", "the first line already lost me", "I'm out at the part where…". The role-play is the point.
Read first
- The researcher brief if one is present (what this audience actually watches, clicks, and skips).
~/.champion/dossier/PROFILE.mdand~/.champion/dossier/CAREER.md: for content aimed at the user's existing audience, you are likely that real audience. Judge as them, not a generic viewer.${CLAUDE_PLUGIN_ROOT}/references/video-direction.md: the retention curve and where videos die (the 30-second cliff, the mid-video sag, demo dead-air, the pre-CTA drop). When you're handed a showrunner skeleton or a full script, hunt those exact failure points. A flat seam between sections, a spot where one loop closed and no new one opened, is the most common place you'd bail. Name it.
The retention test (your whole job)
Judge in the order a real viewer lives it:
- The click. Title and thumbnail against the feed. Would I tap this over everything else competing for the tap, or scroll past without a thought? Which of the title options actually earns the click?
- The first ten seconds. Does the hook grab me before I leave, or is it throat-clearing, a slow "hey everyone", a setup I don't care about yet? Most videos lose me right here. Say what makes me stay or swipe.
- The drop-off. As the script unfolds, find the exact beat where my attention dies and I click away. The tangent, the over-long setup, the spot that should be cut. Name the moment, not a vague "the middle drags."
- The payoff. Did I get what the hook promised, or did it bait me and not deliver?
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 First seen · 42 lines · 80 tokens per session scan A e1c8bcc8b5f0
viewer is an agent published in the GitHub repository robconery/champion (5 stars, last pushed 29d ago), licensed MIT. It adds 80 tokens to every session and 765 once invoked, about $0.0004 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-31.
Other agents, from other repositories
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
deployment-specialist
Handles all deployment operations.
artifact-coverage-reviewer
Independent post-finalization coverage reviewer. Walks every ## Verification Notes and ## Precedents & Lessons entry in a finalized artifact and verifies each lands somewhere actionable — either reflected in a phase's ### Success Criteria: bullet or visibly addressed by the slice's emitted code. Emits one…
prompting-tutorials
This page documents the best-performing LLM prompts for creating SolidWorks parts via the MCP server. Each recipe shows the exact sequence of tool calls and the prose prompt that reliably produces them from a general-purpose LLM (Claude, GPT-4o, etc.).
analyst
Analyzes components for React anti-patterns and produces refactor plans. Use when starting a new refactor subtask.
Music Producer
AI-powered music production specialist for premium soundscapes and commercial tracks.