ReddRadar
Agent skill
agent-detector
CRITICAL: MUST run for EVERY message. Detects agent, complexity, AND model automatically. Always runs FIRST.
Install this agent skill to your Project
npx add-skill https://github.com/nguyenthienthanh/aura-frog/tree/main/aura-frog/skills/agent-detector
SKILL.md
Aura Frog Agent Detector
Priority: HIGHEST - Runs FIRST for every message
When to Use
ALWAYS - Every user message, no exceptions.
Auto-Complexity Detection
AI auto-detects task complexity. User doesn't need :fast or :hard variants.
Complexity Levels
complexity[3]{level,criteria,approach}:
Quick,Single file/Simple fix/Clear scope,Direct implementation - skip research
Standard,2-5 files/Feature add/Some unknowns,Scout first then implement
Deep,6+ files/Architecture/Vague scope,Research + plan + implement
Auto-Detection Criteria
Quick (1-2 tool calls):
- Typo fix, single variable rename
- Add console.log/debugging
- Simple CSS change
- Clear file path given
- "Just do X" explicit instruction
Standard (3-6 tool calls):
- New component/function
- Bug fix with clear error
- API endpoint addition
- File modification with tests
Deep (7+ tool calls, use workflow-orchestrator):
- New feature across multiple files
- Refactoring/architecture change
- Vague requirements ("make it better")
- Security audit
- Performance optimization
- User asks to "plan" or "design"
Detection Logic
1. Count mentioned files/components
2. Check for vague vs specific language
3. Detect scope modifiers (all, entire, every)
4. Check for research keywords (how, why, best way)
5. Assign complexity level
Model Selection
Auto-select model based on task complexity and agent type.
Model Mapping
model_selection[3]{model,when_to_use,agents}:
haiku,Quick tasks/Simple queries/Orchestration,lead/scanner
sonnet,Standard implementation/Coding/Testing/Bug fixes,All dev agents/tester/frontend
opus,Architecture/Deep analysis/Security audits/Complex planning,security (audits)/Any agent (architecture mode)
Complexity → Model
complexity_model[3]{complexity,default_model,override_to_opus}:
Quick,haiku,Never
Standard,sonnet,User asks for architecture/design
Deep,sonnet,Always consider opus for planning phase
Task Type → Model
task_model[8]{task_type,model,reason}:
Typo fix / config change,haiku,Minimal reasoning needed
Bug fix / feature add,sonnet,Standard implementation
API endpoint / component,sonnet,Standard implementation
Test writing,sonnet,Requires code understanding
Code review,sonnet,Pattern matching + analysis
Architecture design,opus,Complex trade-off analysis
Security audit,opus,Deep vulnerability analysis
Refactoring / migration,opus,Cross-cutting impact analysis
Agent Default Models
agent_models[10]{agent,default_model,opus_when}:
lead,haiku,Never (orchestration only)
scanner,haiku,Never (detection/context loading)
router,haiku,Never (routing only)
architect,sonnet,Schema design / migration planning / system architecture
frontend,sonnet,Design system architecture
mobile,sonnet,Architecture decisions
strategist,sonnet,Business strategy / ROI evaluation
security,sonnet,opus for full audits
tester,sonnet,Never
devops,sonnet,Infrastructure architecture
Model Selection Output
Include in detection result:
## Detection Result
- **Agent:** architect
- **Model:** sonnet
- **Complexity:** Standard
- **Reason:** API endpoint implementation
When spawning Task tool, use the detected model:
Task(subagent_type="architect", model="sonnet", ...)
Multi-Layer Detection System
Layer 0: Task Content Analysis (Highest Priority)
Analyze the actual task, not just the repo. A backend repo may have frontend tasks (templates, PDFs, emails).
Full patterns: task-based-agent-selection.md
task_content_triggers[7]{category,example_patterns,activates,score_boost}:
Frontend,html template/blade/twig/email template/pdf styling/css,frontend,+50 to +60
Backend,api endpoint/controller/middleware/queue job/webhook,architect (+ framework skill),+50 to +55
Database,migration/schema/query optimization/slow query/n+1,architect,+55 to +60
Security,xss/sql injection/csrf/vulnerability/auth bypass,security,+55 to +60
DevOps,docker/kubernetes/ci-cd/terraform/deployment,devops,+50 to +55
Testing,unit test/e2e test/coverage/mock/fixture,tester,+45 to +55
Design,figma/wireframe/design system/accessibility,frontend,+50 to +60
Key insight: Task content score ≥50 → Override or co-lead with repo-based agent.
Examples:
# Backend repo, but frontend task
Repo: Laravel API
Task: "Fix email template styling"
→ frontend (PRIMARY) + architect (SECONDARY)
# Frontend repo, but backend task
Repo: Next.js
Task: "Add rate limiting to API route"
→ architect (PRIMARY) + frontend (SECONDARY)
Layer 1: Explicit Technology Detection
Check if user directly mentions a technology:
tech_detection[10]{technology,keywords,agent,score}:
React Native,react-native/expo/RN,mobile,+60
Flutter,flutter/dart/bloc,mobile-flutter,+60
Angular,angular/ngrx/rxjs,web-angular,+60
Vue.js,vue/vuejs/pinia/nuxt,web-vuejs,+60
React,react/reactjs/jsx,web-reactjs,+60
Next.js,next/nextjs/ssr/ssg,web-nextjs,+60
Node.js,nodejs/express/nestjs/fastify,architect,+60
Python,python/django/fastapi/flask,backend-python,+60
Go,go/golang/gin/fiber,backend-go,+60
Laravel,laravel/php/eloquent/artisan,backend-laravel,+60
Layer 2: Intent Detection Patterns
Detect user intent from action keywords:
intent_detection[8]{intent,keywords,primary,secondary}:
Implementation,implement/create/add/build/develop,Dev agent,frontend/tester
Bug Fix,fix/bug/error/issue/broken/crash,Dev agent,tester
Testing,test/testing/coverage/QA/spec,tester,Dev agent
Design/UI,design/UI/UX/layout/figma/style,frontend,Dev agent
Database,database/schema/query/migration/SQL,architect,Backend agent
Security,security/vulnerability/audit/owasp/secure,security,Dev agent
Performance,performance/slow/optimize/speed/memory,devops,Dev agent
Deployment,deploy/docker/kubernetes/CI-CD/pipeline,devops,-
Layer 3: Project Context Detection
Read project files to infer tech stack:
project_detection[10]{file,indicates,agent,score}:
app.json (with expo),React Native,mobile,+40
pubspec.yaml,Flutter,mobile-flutter,+40
angular.json,Angular,web-angular,+40
*.vue files,Vue.js,web-vuejs,+40
next.config.js,Next.js,web-nextjs,+40
package.json + react (no next),React,web-reactjs,+40
package.json + express/nestjs,Node.js,architect,+40
requirements.txt/pyproject.toml,Python,backend-python,+40
go.mod/go.sum,Go,backend-go,+40
artisan/composer.json + laravel,Laravel,backend-laravel,+40
Layer 4: File Pattern Detection
Check recent files and naming conventions:
file_patterns[9]{pattern,agent,score}:
*.phone.tsx/*.tablet.tsx,mobile,+20
*.dart/lib/ folder,mobile-flutter,+20
*.component.ts/*.service.ts,web-angular,+20
*.vue,web-vuejs,+20
app/route.ts (Next.js),web-nextjs,+20
*.controller.ts/*.module.ts,architect,+20
views.py/models.py,backend-python,+20
*.go,backend-go,+20
*Controller.php/*Model.php,backend-laravel,+20
Scoring Weights
weights[9]{criterion,weight,description}:
Task Content Match,+50-60,Task-based patterns override repo (Layer 0) - HIGHEST PRIORITY
Explicit Mention,+60,User directly mentions technology
Keyword Exact Match,+50,Direct keyword match to intent
Project Context,+40,CWD/file structure/package files
Semantic Match,+35,Contextual/implied match
Task Complexity,+30,Inferred complexity level
Conversation History,+25,Previous context/active agents
File Patterns,+20,Recent files/naming conventions
Project Priority Bonus,+25,Agent in project-config.yaml priority list
Task Content Override Rule: When task content score ≥50 for a different domain than the repo, that domain's agent becomes PRIMARY or co-PRIMARY.
Agent Thresholds
thresholds[4]{level,score,role}:
Primary Agent,≥80,Leads the task
Secondary Agent,50-79,Supporting role
Optional Agent,30-49,May assist
Not Activated,<30,Not selected
QA Agent Conditional Activation
tester is ALWAYS Secondary when:
- Intent = Implementation (+30 pts as secondary)
- Intent = Bug Fix (+35 pts as secondary)
- New feature being created
- Code modification requested
tester is Primary when:
- Intent = Testing (keywords: test, coverage, QA)
- User explicitly asks for tests
- Coverage report requested
tester is SKIPPED when:
- Pure documentation task
- Pure design discussion (no code)
- Research/exploration only
Detection Process
Pre-Step: Check Detection Cache (Performance Optimization)
Before running full detection, check if a cached result can be reused.
Cache file: .claude/cache/agent-detection-cache.json
cache_check[4]{condition,action}:
Cache exists AND same workflowId AND phase > 1,Use cached result (skip Steps 0-5)
Cache exists AND same workflowId AND phase = 1,Invalidate — re-detect (requirements may change agents)
New workflow OR no workflowId,Invalidate — full detection
User override (e.g. "Use tester"),Invalidate — honor explicit override
Cache hit output:
## Detection Result (cached)
- **Agent:** [cached-agent]
- **Model:** [cached-model]
- **Complexity:** [cached-complexity]
- **Cache:** hit (workflow: [id], phase: [N])
Cache write: After completing Steps 0-5, write detection result to cache file:
{
"workflowId": "FEAT-123",
"agent": "architect",
"model": "sonnet",
"complexity": "Standard",
"secondary": ["tester"],
"teamMode": false,
"detectedAt": "2026-03-24T10:00:00Z"
}
Savings: ~500-1000 tokens per message after first detection in a workflow.
Step 0: Task Content Analysis (Do This First!)
Analyze the task itself before checking the repo.
User: "Update the invoice PDF layout - table breaks across pages"
Task Analysis:
- "PDF" → Frontend task pattern (+50)
- "layout" → Frontend keyword (+40)
- "table" → Frontend keyword (+30)
→ Total frontend score: 120 pts → frontend is PRIMARY
Even if repo is pure backend, frontend leads this task!
Apply patterns from: task-based-agent-selection.md
Step 1: Extract Keywords
User: "Fix the login button not working on iOS"
Extracted:
- Action: "fix" → Bug Fix intent
- Component: "login button" → UI element
- Platform: "iOS" → Mobile
- Issue: "not working" → Bug context
Step 2: Check Project Context (Use Cached Detection!)
IMPORTANT: Use cached project detection to avoid re-scanning every task.
# 1. Check detection first (fast path):
.claude/project-contexts/[project-name]/project-detection.json
# 2. If detection valid (< 24h, key files unchanged):
→ Use cached: framework, agents, testInfra, filePatterns
# 3. If detection invalid or missing:
→ Run full detection (reads package.json, etc.)
→ Save to project-contexts for next task
# 4. Load project-specific overrides:
.claude/project-contexts/[project]/project-config.yaml
.claude/project-contexts/[project]/conventions.md
Detection invalidation triggers:
- Key config files changed (package.json mtime/size)
- Detection older than 24 hours
- User runs
/project:refresh
Commands:
/project:status- Show project detection/project:refresh- Force fresh scan
Step 3: Score All Agents (Combine Task + Repo)
mobile:
- "iOS" keyword: +35 (semantic)
- CWD = /mobile-app: +40 (context)
- Recent *.phone.tsx: +20 (file pattern)
→ Total: 95 pts ✅ PRIMARY
tester:
- Bug fix intent: +35 (secondary for bugs)
→ Total: 35 pts ✅ OPTIONAL
frontend:
- "button" keyword: +20 (UI element)
→ Total: 20 pts ❌ NOT SELECTED
Step 4: Select Agents
- Primary: Highest score ≥80
- Secondary: Score 50-79
- Optional: Score 30-49
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
nguyenthienthanh/aura-frog
scalable-thinking
Design for scale while keeping implementation simple (KISS).
nguyenthienthanh/aura-frog
debugging
Systematic debugging with root cause investigation. NO fixes without understanding cause first.
nguyenthienthanh/aura-frog
migration-helper
Guide safe database and code migrations with zero-downtime strategies.
nguyenthienthanh/aura-frog
testing-patterns
Unified testing patterns across all frameworks. Provides consistent test structure, naming, and best practices for Jest, Vitest, Pytest, PHPUnit, Go testing, and more.
nguyenthienthanh/aura-frog
phase1-lite
Ultra-compact Phase 1 requirements output. HARD CAP: 500 tokens.
nguyenthienthanh/aura-frog
stitch-design
Generate UI designs using Google Stitch AI with optimized prompts
Didn't find tool you were looking for?