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/nickcrew/claude-cortex/build-optimizationnpx skills add NickCrew/Claude-Cortex --skill build-optimizationgit clone --depth 1 https://github.com/NickCrew/Claude-CortexWrote 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/nickcrew/claude-cortex/build-optimization)<a href="https://agentmods.dev/skills/nickcrew/claude-cortex/build-optimization"><img src="https://agentmods.dev/badge/skills/nickcrew/claude-cortex/build-optimization.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 | $0.00034 | $0.00671 |
| Opus 5 | $0.00017 | $0.00336 |
| Sonnet 5 | $0.00007 | $0.00134 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
build-optimization 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 today.
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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Optimization
Expert guidance for optimizing build systems, reducing compilation times, maximizing cache hit rates, and building developer tools that enhance productivity across the development lifecycle.
When to Use This Skill
- Diagnosing slow build times and identifying bottlenecks
- Configuring caching strategies (local, remote, distributed)
- Setting up incremental builds and parallel execution
- Optimizing CI/CD pipeline performance and cost
- Designing or improving bundle splitting and tree shaking
- Building CLIs, plugins, code generators, or IDE extensions
- Configuring monorepo tooling (Nx, Turborepo, Bazel)
- Reducing developer feedback loop times (hot reload, watch mode)
- Managing build artifacts and reproducibility
Quick Reference
| Task | Load reference |
|---|---|
| Compilation, caching, incremental builds, CI/CD optimization | skills/build-optimization/references/build-systems.md |
| Plugin systems, code generation, linting, IDE integration, monorepo tooling | skills/build-optimization/references/developer-tooling.md |
Core Targets
- Build time under 30 seconds for development builds
- Rebuild time under 5 seconds with watch mode
- Cache hit rate above 90% in CI
- Zero flaky builds in production pipelines
- Reproducible builds across environments
Workflow
1. Performance Analysis
Profile the current build before making changes.
- Measure cold build, incremental rebuild, and hot reload times
- Profile CPU, memory, and I/O during builds
- Map the dependency graph and identify bottlenecks
- Evaluate cache hit rates and invalidation patterns
- Review current tool configuration for missed optimizations
2. Optimization
Apply targeted improvements based on profiling data.
- Enable incremental compilation and caching
- Configure parallel execution across available cores
- Set up code splitting and tree shaking
- Optimize module resolution and source transformation
- Implement remote or distributed caching for CI
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.
- today First seen · 95 lines · 34 tokens per session scan A 164ee58e621b
build-optimization is a skill published in the GitHub repository NickCrew/Claude-Cortex (37 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 671 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-09-03.
Other skills, from other repositories
CI Pipeline Optimizer
Optimize CI test pipelines through intelligent test splitting, parallelization, caching strategies, and selective test execution based on code changes.
fix-ci
Fix CI failures and performance regressions for a Julia package PR by iterating - triage the latest CI results, fix one root cause, verify locally, push. Use when a PR's GitHub Actions or Buildkite CI is failing, or when CI jobs run slower than they do on the main branch. Verifies CPU and GPU compilation locally…
dockerfile-slimming
Reduce container image size and build time with multi-stage builds and ordered layer caching.
testing-cicd-integration
Skill for integrating testing frameworks with CI/CD pipelines with specsmith governance.
performance-optimization
Optimizes application performance. Use when performance requirements exist, when you suspect performance regressions, or when Core Web Vitals or load times need improvement. Use when profiling reveals bottlenecks that need fixing.
infra-audit
Infrastructure and CI/CD security audit - GitHub Actions workflows (pwn-request, secret logging, missing pinning, permissions overreach), Dockerfile (latest tag, USER root, ADD on URL), Kubernetes manifests (runAsNonRoot, privileged containers, hostNetwork), Terraform (IAM wildcards, state in git, module pinning)…