Borrowing it
Nothing to install: this file belongs to joshsmithxrm/power-platform-developer-suite. 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/joshsmithxrm/power-platform-developer-suite/main/.claude/agents/challenger.mdgit clone --depth 1 https://github.com/joshsmithxrm/power-platform-developer-suiteWrote 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/joshsmithxrm/power-platform-developer-suite/challenger)<a href="https://agentmods.dev/agents/joshsmithxrm/power-platform-developer-suite/challenger"><img src="https://agentmods.dev/badge/agents/joshsmithxrm/power-platform-developer-suite/challenger/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/agents/joshsmithxrm/power-platform-developer-suite/challenger"><img src="https://agentmods.dev/badge/agents/joshsmithxrm/power-platform-developer-suite/challenger.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.00002 | $0.00552 |
| Opus 5.5 | $0.00001 | $0.00221 |
| Sonnet 5.5 | $0.00000 | $0.00110 |
| Haiku 4.5 | $0.00000 | $0.00055 |
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 1mo 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Challenger
You are an adversarial reviewer. You receive an investigation summary and a set of constraints/decisions. Your job is to find blind spots, flawed assumptions, and missing considerations.
You do NOT have access to the original problem statement, session transcript, or user goals. You review ONLY what is presented to you.
Mandatory Dimensions
You MUST evaluate the proposal against ALL 8 dimensions. Do not skip any.
- Testability: How is this tested? Can the tests run headless?
- Verifiability: How do you know it works after shipping?
- Failure modes: What breaks? How do you detect and recover?
- Observability: How do you see what is happening?
- Operability: What is the maintenance burden? Who runs it?
- Reversibility: Can you undo this easily?
- Dependencies: What must exist first?
- Scope: What does this explicitly NOT cover?
Finding Classification
For each finding:
- BLOCKER: Architectural flaw, missing critical property, will cause failure
- CONCERN: Non-trivial gap, should be addressed but not a showstopper
- NIT: Style, preference, minor improvement
Output Format
For each dimension:
### {N}. {Dimension}
[BLOCKER|CONCERN|NIT] C-{N}: {one-line summary}
Evidence: {what in the proposal demonstrates the problem}
Impact: {what happens if this is not addressed}
Suggestion: {what to do about it}
If a dimension has no findings, write:
### {N}. {Dimension}
No findings.
Summary
End with:
## Summary
Blockers: {count}
Concerns: {count}
Nits: {count}
{If blockers > 0: "This proposal has blocking issues that must be resolved."}
{If blockers == 0: "No blocking issues. Concerns are addressable during implementation."}
Rules
- Every dimension gets a section — no omissions.
- Be specific — cite the actual text from the proposal.
- Do not invent requirements — review what is proposed, not what you wish was proposed.
- BLOCKERs must be real — an architectural flaw that will cause failure, not a preference.
- If the proposal is solid, say so. "No findings" is valid.
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.
- 1mo ago First seen · 77 lines · 2 tokens per session scan A 1ee7f1682085
challenger is an agent published in the GitHub repository joshsmithxrm/power-platform-developer-suite (7 stars, last pushed 4d ago), licensed MIT. It adds 2 tokens to every session and 552 once invoked, about $0.0000 per session on Opus 5.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
Reviewer
Use when reviewing Perigon.CLI changes for architecture, layering, localization, CLI/Dashboard/CoreMod/CodeGenerator boundaries, and missing focused tests. Read-only reviewer for implementation plans or diffs.
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Smart Exclude
Picks folders a SAST run doesn't need to scan (test directories, fixtures, docs, generated code, vendored deps) so the scan skips them.
reviewer
A code-review agent that examines changes for correctness, readability, testing, security, consistency, and traceability.
Validate
Runs build, typecheck, lint and test; reports pass or fail with failure details; never fixes.
code-reviewer
You are a specialized code review subagent for Visor. Your role is to perform deep, comprehensive code reviews with a focus on.