Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add acaprino/daodan/plugin install codebase-xrayWrote 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/acaprino/daodan/analyze)<a href="https://agentmods.dev/skills/acaprino/daodan/analyze"><img src="https://agentmods.dev/badge/skills/acaprino/daodan/analyze.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.00122 | $0.06167 |
| Opus 5 | $0.00061 | $0.03083 |
| Sonnet 5 | $0.00024 | $0.01233 |
| Haiku 4.5 | $0.00012 | $0.00617 |
Grade C, and why
analyze scanned grade C with 1 finding 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 5d 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
The analysis NEVER reads or includes contents from sensitive files: `.env`, `.env.*`, `credentials.*`, `secrets.*`, `*.pem`, `*.key`, `*.p12`, `*.pfx`, `id_rsa*`, `id_ed25519*`, `.npmrc`, `.pypirc`, `.netrc`, or any file How it starts
The opening of the file, as written. The whole thing — 485 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase X-Ray Analysis Skill
Overview
This skill combines mechanical structure extraction with Claude's semantic understanding to produce comprehensive codebase documentation. Unlike simple AST parsing, this skill captures:
- WHAT the code does (structure, functions, classes)
- WHY it exists (business purpose, design decisions)
- HOW it integrates (dependencies, contracts, flows)
- CONSEQUENCES of changes (side effects, failure modes)
Language Support
| Language | Extensions | Structural extraction | Comment rewriting |
|---|---|---|---|
| Python | .py, .pyi |
stdlib ast (always available) |
# line + docstrings |
| Java | .java |
tree-sitter (preferred) or regex | //, /* */, Javadoc /** */ |
| JavaScript | .js, .mjs, .cjs, .jsx |
tree-sitter (preferred) or regex | //, /* */, JSDoc /** */ |
| TypeScript | .ts, .tsx, .mts, .cts |
tree-sitter (preferred) or regex; adds interfaces, enums, type aliases | //, /* */, JSDoc /** */ |
| SQL | .sql, .ddl, .dml |
regex DDL (tables, views, indexes, sequences, types, functions, procedures, triggers) | --, /* */ |
| PL/SQL (Oracle) | .pks, .pkb, .plsql, .pls, .pck, .prc, .fnc, .trg |
regex (packages, package bodies, type bodies, cursors, exceptions, %TYPE/%ROWTYPE references) | --, /* */ |
| Rust | .rs |
tree-sitter (preferred) or regex; structs, enums, traits, impls (with Trait for Type naming), mods, unions, type aliases |
//, /* */, rustdoc /// / //! / /** */ / /*! */ |
.sql files are disambiguated against PL/SQL by inspecting content for Oracle-specific markers (CREATE OR REPLACE PACKAGE, DBMS_OUTPUT, %TYPE, %ROWTYPE, UTL_FILE, PRAGMA AUTONOMOUS, etc.). PostgreSQL plpgsql is correctly classified as SQL.
Prerequisites
The scripts require Python >= 3.10 and work out of the box with just the stdlib. Tree-sitter is optional and improves accuracy for Java / JavaScript / TypeScript / Rust:
What ships with it
25 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.
- references/AI_ANALYSIS_METHODOLOGY.md 12 KB
- references/analysis-templates.md 6.7 KB
- references/ANTIREZ_COMMENTING_STANDARDS.md 14 KB
- references/SEMANTIC_PATTERNS.md 13 KB
- scripts/analyze_file.py 14 KB runs code
- scripts/ast_parser.py 3.1 KB runs code
- scripts/classifier.py 10 KB runs code
- scripts/comment_rewriter.py 36 KB runs code
- scripts/doc_review.py 44 KB runs code
- scripts/languages/__init__.py 5.2 KB runs code
- scripts/languages/_treesitter.py 4.9 KB runs code
- scripts/languages/base.py 5.7 KB runs code
- scripts/languages/comments.py 15 KB runs code
- scripts/languages/java.py 16 KB runs code
- scripts/languages/javascript.py 19 KB runs code
- scripts/languages/plsql.py 6.7 KB runs code
- scripts/languages/python.py 14 KB runs code
- scripts/languages/rust.py 20 KB runs code
- scripts/languages/sql.py 8.9 KB runs code
- scripts/languages/typescript.py 7.5 KB runs code
- scripts/requirements.txt 1.0 KB
- scripts/rewrite_comments.py 24 KB runs code
- scripts/usage_finder.py 14 KB runs code
- templates/analysis_report.md 1.5 KB
- templates/semantic_analysis.md 6.9 KB
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.
- 5d ago First seen · 485 lines · 122 tokens per session scan C 9fb0a23aaabf
analyze is a skill published in the GitHub repository acaprino/daodan (8 stars, last pushed yesterday), licensed MIT. It adds 122 tokens to every session and 6,167 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…