Borrowing it
Nothing to install: this file belongs to TheWayWithin/agent-11. 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/TheWayWithin/agent-11/main/.claude/commands/recon.mdgit clone --depth 1 https://github.com/TheWayWithin/agent-11Wrote 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/commands/thewaywithin/agent-11/recon)<a href="https://agentmods.dev/commands/thewaywithin/agent-11/recon"><img src="https://agentmods.dev/badge/commands/thewaywithin/agent-11/recon/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/commands/thewaywithin/agent-11/recon"><img src="https://agentmods.dev/badge/commands/thewaywithin/agent-11/recon.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.00014 | $0.00768 |
| Opus 5.5 | $0.00006 | $0.00307 |
| Sonnet 5.5 | $0.00003 | $0.00154 |
| Haiku 4.5 | $0.00001 | $0.00077 |
Grade A, and why
recon 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.
This is a copy
84% identical to design-review — 126 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
RECON PROTOCOL ACTIVATION 🎯
You are now executing a UI/UX reconnaissance mission using the RECON Protocol (Rapid Evaluation & Critique Operations Network). Your objective is to conduct a comprehensive design assessment of the current changes.
OPERATIONAL CONTEXT
GIT STATUS:
!`git status`
FILES MODIFIED:
!`git diff --name-only origin/HEAD...`
RECENT OPERATIONS:
!`git log --no-decorate --oneline -10 origin/HEAD...`
CHANGE ANALYSIS:
!`git diff --merge-base origin/HEAD`
MISSION PARAMETERS
Review the complete diff above containing all UI/UX changes. Execute the RECON Protocol to assess design quality, user experience, accessibility, and visual consistency.
EXECUTION DIRECTIVE
- Deploy @designer agent with RECON Protocol activation
- If UI doctrine exists in
/field-manual/ui-doctrine.md, apply those standards - If design tokens exist in
/field-manual/combat-tokens.md, verify compliance - Execute all 8 phases of RECON Protocol systematically
- Classify findings by threat level: [CRITICAL], [URGENT], [TACTICAL], [COSMETIC]
- Apply "Observe-Don't-Prescribe" communication doctrine
- Provide screenshot evidence for all visual issues
PRIORITY ASSESSMENT AREAS
- User flow disruptions
- Accessibility violations (WCAG AA+)
- Responsive design failures
- Visual inconsistencies
- Performance degradation
- Brand compliance issues
- Component reuse patterns
- Design token violations
OUTPUT REQUIREMENTS
Your final response must contain:
- The complete RECON REPORT in markdown format
- Evidence screenshots where applicable
- Prioritized recommendations
- Overall design health assessment
COORDINATION NOTES
- If testing functionality needed, coordinate with @tester's SENTINEL Mode
- If architecture concerns arise, escalate to @architect
- If performance issues detected, alert @operator
- For accessibility deep-dive, may require specialist consultation
INITIATE RECON PROTOCOL NOW
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 · 75 lines · 14 tokens per session scan A 6703cd1d5c9e
recon is a command published in the GitHub repository TheWayWithin/agent-11 (17 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 768 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 84% identical to design-review, differing in 126 lines, and is treated as a copy.
Other commands, from other repositories
muggle-ai-teams
Adaptive agent team orchestration. Coordinates Frontend Engineer, Backend Engineer, General Engineer, UX Reviewer, and Reviewer agents through design, implementation, review, and learning phases.
multi-execute
Multi-model collaborative execution — route tasks to Codex (backend) and/or Gemini (frontend), acquire prototypes, refactor to production-grade, and audit with dual-model review.
design-import
Scaffolds React components from a Claude Design handoff bundle and stops at files on disk: no stories, no tests, no pull request. Use when handed a claude.ai/design URL or a local bundle file; when that same scaffold should carry on through test generation, browser verification and an opened PR, run /ork:design-ship…
design-ship
One-shot pipeline turning a claude.ai/design link into a pull request: scaffold via /ork:design-import, stories and specs via /ork:cover, browser verification via /ork:expect, then open the PR. Use when a design link should come back as a PR with no intermediate steps; if all you need is the components written to…
critique
Design lens critique covering visual hierarchy, clarity, and anti-slop patterns — produces a findings table, no code edits unless asked. Use when the user wants a design review, says "what's wrong with this UI", or needs a second opinion before a handoff or presentation.
audit
A project review command that checks both the user interface and the code. It can inspect design rules, accessibility, performance, security, and code quality at different levels of depth.