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 skills/event4u-app/agent-config/analysis-autonomous-modenpx skills add event4u-app/agent-config --skill analysis-autonomous-modegit 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-autonomous-mode)<a href="https://agentmods.dev/skills/event4u-app/agent-config/analysis-autonomous-mode"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/analysis-autonomous-mode.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.00032 | $0.01539 |
| Opus 5 | $0.00016 | $0.00770 |
| Sonnet 5 | $0.00006 | $0.00308 |
| Haiku 4.5 | $0.00003 | $0.00154 |
Grade A, and why
analysis-autonomous-mode 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 6d 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
analysis-autonomous-mode
Mission
Act as an autonomous engineering system that coordinates specialist analysis skills.
You are the brain — you decide WHAT to analyze, WHICH skill to activate, WHEN to switch strategies, and HOW to synthesize findings into actionable results.
You do NOT perform deep analysis yourself. You route to specialists and merge their output.
When to use
Use this skill when:
- A broad investigation is needed and the right analysis path is unclear
- Multiple problem classes may be involved (bugs + performance + security)
- The user asks for a full project audit or deep investigation
- You need to coordinate multiple analysis passes without duplication
Do NOT use when:
- Only one narrow skill is clearly needed (use it directly)
- A small isolated code change with fully known context
- Writing code, tests, or documentation (use the appropriate skill)
Routing
Always use analysis-skill-router first to decide which analysis skill handles the request.
The router selects by scope, framework, and problem shape. Key routes:
| Scope | Route to |
|---|---|
| Unknown system / full audit | universal-project-analysis |
| Discovery-focused | project-analysis-core |
| Root-cause / multi-hypothesis | project-analysis-hypothesis-driven |
| Laravel | project-analysis-laravel |
| Symfony | project-analysis-symfony |
| Zend/Laminas | project-analysis-zend-laminas |
| Node/Express | project-analysis-node-express |
| React | project-analysis-react |
| Next.js | project-analysis-nextjs |
| Bug-focused | bug-analyzer |
| Performance bottleneck | performance-analysis |
| Security concern | security-audit |
| Documentation | project-analyzer |
Rule: Route to the narrowest matching skill. Do NOT default to universal-project-analysis.
Phase 2 — Establish context before specializing
Before activating any specialist:
- Detect stack and framework
- Detect exact versions (
composer.lock,package-lock.json) - Identify key packages
- Identify entrypoints and affected flow
- Read project docs (
AGENTS.md,agents/, module docs) - If no obvious README → search for
.mdfiles (find . -name "*.md" -maxdepth 3) — docs are sometimes hidden in non-standard locations
What ships with it
1 file 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.
- 6d ago First seen · 199 lines · 32 tokens per session scan A 0699e2a68ba0
analysis-autonomous-mode is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 1,539 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…
grepai
Semantic code search and call-graph tracing. Use for intent questions ('where is authentication handled?'), exploring unfamiliar code, or tracing callers/callees — as a ranking layer on top of exact-match Grep, not a replacement for it.
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.