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 quangphu1912/codebase-analyzer --skill analyze-build-pipelinegit clone --depth 1 https://github.com/quangphu1912/codebase-analyzerWrote 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/quangphu1912/codebase-analyzer/analyze-build-pipeline)<a href="https://agentmods.dev/skills/quangphu1912/codebase-analyzer/analyze-build-pipeline"><img src="https://agentmods.dev/badge/skills/quangphu1912/codebase-analyzer/analyze-build-pipeline.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.00033 | $0.01301 |
| Opus 5 | $0.00016 | $0.00651 |
| Sonnet 5 | $0.00007 | $0.00260 |
| Haiku 4.5 | $0.00003 | $0.00130 |
Grade A, and why
analyze-build-pipeline 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Announce at start: "Using codebase-analyzer to analyze the build pipeline."
Overview
Trace the source -> runtime transformation pipeline. Find filtering, compilation, code generation, and build-time shaping.
Prerequisite: Reads docs/analysis/provenance.md (from trace-codebase-provenance).
Process
- Identify build config files (webpack.config, vite.config, tsconfig, Cargo.toml, Makefile)
- Map build stages: lint -> compile -> bundle -> optimize -> package -> deploy
- Find code filtering: what gets included/excluded by build conditions
- Identify code generation: Protobuf, GraphQL, OpenAPI generators
- Find build-time constants injected into code
- Trace environment variable usage in build
- Produce build pipeline map with filtering report
Quick Reference
| Build Tool | Config Location | Key Features |
|---|---|---|
| webpack | webpack.config.* | Loaders, plugins, code splitting |
| Vite | vite.config.* | Plugins, define, env replacement |
| esbuild | build script | Bundle, define, external |
| Cargo | Cargo.toml | Features, profiles, build scripts |
| Make | Makefile | Targets, variables, recipes |
| Bazel | BUILD, WORKSPACE | Rules, targets, toolchains |
Trigger Signals
- HIGH confidence: Build conditions that filter tools/capabilities ->
extract-tool-graph - HIGH confidence: Environment-specific code paths -> affects all downstream analysis
- MEDIUM confidence: Code generation step -> provenance verified
- LOW confidence: Standard build, no filtering -> no additional deep dive
Transformation Chain Reasoning
Map the full chain: source -> preprocessor -> compiler -> bundler -> optimizer -> minifier -> output. At each stage: what's added? what's removed? what's transformed? The chain reveals what the final artifact went through.
Every transformation stage is a decision point where code is shaped. A TypeScript file does not become runtime JavaScript unchanged -- it passes through tsc (type stripping), possibly babel (target downleveling), webpack/vite (bundling + tree-shaking), a minifier (whitespace + identifier mangling), and potentially a compressor (gzip/brotli). Each stage introduces gaps between what you read in source and what actually executes.
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.
- 7d ago First seen · 113 lines · 33 tokens per session scan A 834bedea7137
analyze-build-pipeline is a skill published in the GitHub repository quangphu1912/codebase-analyzer (2 stars, last pushed 5mo ago), licensed MIT. It adds 33 tokens to every session and 1,301 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
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.
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…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.