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 skills add event4u-app/agent-config --skill analysis-skill-routergit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/skills/event4u-app/agent-config/analysis-skill-router)<a href="https://agentmods.dev/skills/event4u-app/agent-config/analysis-skill-router"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/analysis-skill-router.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.1 | $0.00047 | $0.00966 |
| Opus 5 | $0.00023 | $0.00483 |
| Sonnet 5 | $0.00009 | $0.00193 |
| Haiku 4.5 | $0.00005 | $0.00097 |
Grade A, and why
analysis-skill-router 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 8d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
analysis-skill-router
A chooser, not a worker. It answers exactly one question — which skill — and then gets out of the way. How to actually carry out the work belongs to whichever skill this picks; a chooser that also explains the work reads like its own fallback target, which is the defect this file was cut back from.
When to use
Use this skill when:
- A request may need deep analysis
- It is unclear which analysis skill should be used
- Multiple analysis skills could plausibly apply
- The stack/framework is known but the correct analysis path is unclear
analysis-autonomous-modeneeds a routing decision
Do NOT use when:
- The correct specialist skill is already obvious
- The task is not an analysis task
- The task is normal implementation work without investigation needs
Procedure
1. Classify the scope
Pick one: full project · architecture review · broad multi-layer debugging · framework-specific deep dive · narrow root cause · performance/security specialist · simple local issue.
Broad scope requires a reason. At least one must hold, or the answer is a narrow specialist: the user asked for breadth · the system is unknown · the issue spans layers · architecture must be reconstructed · the cause is non-local.
2. Detect the framework
Laravel · Symfony · Zend/Laminas · Node/Express · React · Next.js · unknown or mixed.
3. Read the decision table
| Signal | Route to |
|---|---|
| Full audit, or unclear stack | universal-project-analysis |
| Unknown system, discovery-focused | project-analysis-core |
| Concrete problem, several plausible causes | project-analysis-hypothesis-driven |
| Bug-focused, not full-project | bug-analyzer |
| Laravel | project-analysis-laravel |
| Symfony | project-analysis-symfony |
| Zend/Laminas | project-analysis-zend-laminas |
| Node/Express | project-analysis-node-express |
| React state / render / hooks | project-analysis-react |
| Next.js SSR / cache / hydration | project-analysis-nextjs |
| Bottleneck | performance-analysis |
| Security concern | security-audit |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 109 lines · 47 tokens per session scan A 6464c88020d7
analysis-skill-router is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 966 once invoked, about $0.0002 per session on Opus 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 skills, from other repositories
diagnose-backend-bug
Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
Concurrency Testing Patterns
Testing concurrent code including race condition detection, deadlock prevention, thread safety verification, and parallel execution correctness.
kiro-verify-completion
Verify completion and success claims with fresh evidence. Use before claiming a task is complete, a fix works, tests pass, or a feature is ready for GO.
chatcrystal-debug-recall
Recall ChatCrystal memories for debugging tasks involving failing tests, compiler errors, runtime exceptions, dependency issues, environment breakage, or performance regressions. Use when historical root causes, fixes, or pitfalls may accelerate diagnosis before proposing a fix.
roblox-performance
Use when profiling Roblox performance or diagnosing FPS, memory, network, mobile, or hot-path problems.