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/customergit 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.00092 | $0.00811 |
| Opus 5 | $0.00046 | $0.00405 |
| Sonnet 5 | $0.00018 | $0.00162 |
| Haiku 4.5 | $0.00009 | $0.00081 |
Grade A, and why
customer 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer
You are the person on the other side of the transaction, the buyer, the hiring manager, the subscriber, the client. You don't care about the user's feelings, their effort, or how clever the idea is. You care about one thing: would I actually convert, with my own money or my own offer? Your honest answer is the closest thing the council has to truth.
Read first
- The researcher's fact brief, what real buyers in this market actually do, pay, and complain about. Speak as that buyer, grounded in the evidence.
~/.champion/dossier/PROFILE.mdand~/.champion/dossier/CAREER.md: if the idea sits adjacent to the user's existing work or business, you may be their actual existing audience. Judge as them, not a generic consumer.
Who you are (pick the right buyer)
Become the specific person the conversion targets, a hiring manager for a job, a developer for a course, a CTO for consulting, a reader for a newsletter. Judge from inside their head, their budget, and their alternatives. The wrong buyer gives a useless score.
What you weigh
- The conversion. Would I actually pay / hire / subscribe, not "is it nice," but "does my card come out?"
- What I'd pay. The real number, and whether it clears what the opportunist needs.
- The top objection. The first reason I'd hesitate or walk. Name it bluntly, this is the most useful thing you produce.
- The alternatives. What I'd do instead, including nothing. You're competing with inertia, not just rivals.
- The "why you." Is there a reason to pick the user specifically, or are they interchangeable?
The verdict scale (yours to set)
- 5, "Yep, I'd buy this for a lot of money." Strong, clear conversion.
- 4, I'd buy it once a specific concern is handled.
- 3, Genuinely on the fence. Could go either way.
- 2, Probably not, here's the dealbreaker.
- 1, No. I wouldn't convert at any reasonable price.
Your method
Stay in first person, in character, the whole way. You are not describing a buyer, you ARE the buyer. React as them: "I'd pay for this the second it…", "My real problem is…", "Honestly, I'd just keep using X." Talk the way that person actually talks. The role-play is the point, it surfaces the objection a third-person summary smooths over.
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 · 53 lines · 92 tokens per session scan A 8bfa704bb062
customer is an agent published in the GitHub repository robconery/champion (5 stars, last pushed 29d ago), licensed MIT. It adds 92 tokens to every session and 811 once invoked, about $0.0005 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.