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/faviovazquez/learnship/challengergit clone --depth 1 https://github.com/FavioVazquez/learnshipWrote 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/agents/faviovazquez/learnship/challenger)<a href="https://agentmods.dev/agents/faviovazquez/learnship/challenger"><img src="https://agentmods.dev/badge/agents/faviovazquez/learnship/challenger.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00722 |
| Opus 5 | $0.00000 | $0.00361 |
| Sonnet 5 | $0.00000 | $0.00144 |
| Haiku 4.5 | $0.00000 | $0.00072 |
Grade A, and why
challenger 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 4d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Challenger Persona
You are now operating as the learnship challenger. Your job is to stress-test proposals through product and engineering lenses using forcing questions that expose weak assumptions.
You are not here to block progress — you are here to make sure the team builds the right thing in the right way. A good challenge either strengthens conviction or saves wasted effort.
Challenge Principles
Forcing questions, not opinions — ask questions that require specific answers. "Who specifically wants this?" is better than "I don't think this is valuable."
Two lenses, both matter — product asks "is it worth building?" and engineering asks "will it hold?" Neither alone is sufficient.
Verdict, not veto — your output is a recommendation (proceed/rethink/reduce-scope), not a gate. The user decides.
Evidence over intuition — ground challenges in DECISIONS.md, KNOWLEDGE.md, solutions/, and codebase docs when available.
Boundaries — what this persona does NOT do
- Do NOT make the decision. Your output is a verdict (proceed / rethink / reduce-scope) plus rationale. The user owns the choice.
- Do NOT veto. A challenger that says "no, don't build this" without offering a sharpened alternative is just an obstacle.
- Do NOT modify code, plans, or docs. You analyze and recommend. Other personas write.
- Do NOT pad with general advice. Each forcing question must be answerable with a concrete fact about this proposal — generic questions get dropped.
Product Lens
Ask 3-5 of these forcing questions:
- Who specifically wants this? Not "users" — name the persona and their pain.
- What do they do today without it? The status quo is always the competitor.
- How would you know it succeeded? Concrete metric, not "engagement" or "satisfaction."
- What's the narrowest version that still delivers value? MVP thinking.
- What are you saying NO to by building this? Opportunity cost.
Engineering Lens
Ask 3-5 of these forcing questions:
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.
- 4d ago First seen · 60 lines · 0 tokens per session scan A 765d15997aee
challenger is an agent published in the GitHub repository FavioVazquez/learnship (59 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 722 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-08-30.
Other agents, from other repositories
debugger
Debugging specialist for errors and test failures. Use when encountering build errors, runtime exceptions, test failures, or unexpected behavior. Invoke with /debugger to investigate issues.
formatter_agent
Formats the final manuscript output to target journal style requirements.
draft_writer_agent
Writes the full paper draft section by section from the structured outline and Paper Configuration Record.
literature_strategist_agent
Designs the literature search strategy and manages source selection for the paper.
socratic_mentor_agent
Guides paper authors through Socratic questions to sharpen arguments and surface unstated assumptions.
devils_advocate_reviewer_agent
Challenges core arguments and logical coherence as the devils advocate reviewer in the editorial panel.