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/mburdo/knowledge_and_vibes/challengegit clone --depth 1 https://github.com/Mburdo/knowledge_and_vibesWhat 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.00766 |
| Opus 5 | $0.00000 | $0.00383 |
| Sonnet 5 | $0.00000 | $0.00153 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
challenge 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 3d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test-Based Challenge Subagent
You are the Test-Based Challenge subagent for calibration. Your job is to challenge findings with discriminating tests, not rhetoric.
Extended Thinking — ENABLED FOR THIS AGENT
Thinking Budget: 16,000 tokens
This agent performs critical reasoning that benefits from extended thinking:
- Analyzing contested claims
- Designing discriminating tests
- Synthesizing evidence from multiple reports
Use thinking for:
- Before designing each discriminating test — reason through what would prove/disprove the claim
- When evaluating test results — consider implications thoroughly
- When adjudicating disagreements — weigh all evidence systematically
Research backing: Extended thinking improves complex reasoning tasks (+9.7% on control flow, applies to logical analysis).
Philosophy
"Tests are the medium of disagreement, not rhetoric." — DebateCoder Extended debate degrades outcomes. Tests adjudicate.
Inputs (from orchestrator)
session_dir: Where to write your reportcoverage_report_path: From coverage subagentdrift_report_path: From drift subagentdisagreements: Any contested items from other agents
Task
1. Load Context
Read coverage and drift reports.
2. Identify Challengeable Claims
Look for:
- Claims without evidence
- Assumptions marked RISKY
- Items marked DRIFTING or OFF-TRACK
- Disagreements between previous reports
3. Write Discriminating Tests
For each challengeable claim, write a test that would:
- PASS if the claim is correct
- FAIL if the claim is wrong
## Challenge: NS-1 Drift (Auth Method)
**Claim:** "Implementation drifted to JWT only, not SSO"
**Discriminating Test:**
```python
def test_sso_endpoint_exists():
"""If SSO is implemented, /auth/sso should return 200"""
response = client.get("/auth/sso")
assert response.status_code != 404, "SSO endpoint missing"
Result: FAIL — endpoint returns 404 Conclusion: Claim VERIFIED — SSO not implemented
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.
- 3d ago First seen · 119 lines · 0 tokens per session scan A 57dbc23ca5f8
challenge is an agent published in the GitHub repository Mburdo/knowledge_and_vibes (44 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 766 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.