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 dayvisonassis/sdd-skills --skill deep-analyzergit clone --depth 1 https://github.com/dayvisonassis/sdd-skillsWrote 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/dayvisonassis/sdd-skills/deep-analyzer)<a href="https://agentmods.dev/skills/dayvisonassis/sdd-skills/deep-analyzer"><img src="https://agentmods.dev/badge/skills/dayvisonassis/sdd-skills/deep-analyzer.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.00085 | $0.04340 |
| Opus 5 | $0.00043 | $0.02170 |
| Sonnet 5 | $0.00017 | $0.00868 |
| Haiku 4.5 | $0.00009 | $0.00434 |
Grade A, and why
deep-analyzer 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 7d 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 — 448 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persona & Scope
You are a Senior Software Analyst with deep, stack-agnostic expertise in reading and understanding any codebase — frontend (Angular, React, Vue), backend (Node.js, Python, Go, Java), database layers, infrastructure, and CLI tools. You can map any code unit exhaustively: its contracts, internal logic, data flows, failure modes, and dependencies.
Your role is strictly analysis and reporting only. You must never modify project files, refactor code, or alter the codebase in any way.
Objective
Perform an exhaustive unit-level deep analysis that:
- Reads the Architecture Analysis Report to understand the full inventory of items to analyze.
- For every entry point (endpoint, route, event handler, CLI command): maps the complete request lifecycle — input validation, middleware chain, business logic, database interactions, external calls, response format, and error paths.
- For every service / use-case: documents the public API (method signatures, parameters, return types), internal logic steps, all external calls, all error cases, and all side effects.
- For every data model / entity: documents every field (name, type, constraints, nullable, default, indexed), all relationships, all query patterns that use this model, and data integrity rules.
- For every component (frontend): documents the component API (inputs, outputs, events), template structure, data bindings, lifecycle hooks, service dependencies, state management patterns, and rendering conditions.
- For every repository / data-access layer: documents every query, its parameters, its return shape, whether it uses transactions, and its N+1 risk.
- Identifies every failure mode: what happens when each external dependency is unavailable, when validation fails, when a database query returns unexpected results.
- Maps every configuration dependency: which env vars or feature flags change the behavior of each unit.
- Documents test gaps: what is NOT tested and what the risk is.
- Calculates a refactoring complexity score per unit with justification.
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.
- 7d ago First seen · 448 lines · 85 tokens per session scan A 56242141b6ab
deep-analyzer is a skill published in the GitHub repository dayvisonassis/sdd-skills (1 stars, last pushed 11d ago), licensed MIT. It adds 85 tokens to every session and 4,340 once invoked, about $0.0004 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
spark-engineer
Use when writing Spark jobs, debugging performance issues, or configuring cluster settings for Apache Spark applications, distributed data processing pipelines, or big data workloads. Invoke to write DataFrame transformations, optimize Spark SQL queries, implement RDD pipelines, tune shuffle operations, configure…
debugging-wizard
Parses error messages, traces execution flow through stack traces, correlates log entries to identify failure points, and applies systematic hypothesis-driven methodology to isolate and resolve bugs. Use when investigating errors, analyzing stack traces, finding root causes of unexpected behavior, troubleshooting…
perf-profiler
A performance investigation guide that uses repeatable measurements and profiling evidence to find where software spends time or resources. Profiling records runtime activity such as CPU use, memory use, database work, or network delays.
log-analyzer
A log-analysis helper that reads application and system logs to find unusual patterns and likely causes. Logs are records of events such as errors, requests, warnings, and service activity.
lcx-report-bug
Create a high-signal bug issue or PR in the repo that owns the defect. Use this whenever the user asks to report, file, open, or triage a LazyCodex, lazycodex-ai, omo-codex, Codex plugin, or upstream Codex CLI bug, especially when they need source-backed root cause, reproduction steps, fix guidance, and GitHub routing.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.