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 DavidVujic/my-eca-config --skill making-the-business-case-for-code-healthgit clone --depth 1 https://github.com/DavidVujic/my-eca-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/davidvujic/my-eca-config/making-the-business-case-for-code-health)<a href="https://agentmods.dev/skills/davidvujic/my-eca-config/making-the-business-case-for-code-health"><img src="https://agentmods.dev/badge/skills/davidvujic/my-eca-config/making-the-business-case-for-code-health/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/davidvujic/my-eca-config/making-the-business-case-for-code-health"><img src="https://agentmods.dev/badge/skills/davidvujic/my-eca-config/making-the-business-case-for-code-health.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.00343 |
| Opus 5 | $0.00017 | $0.00171 |
| Sonnet 5 | $0.00007 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
making-the-business-case-for-code-health 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 12d 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.
What it actually says
Making the Business Case for Code Health
Overview
Use this skill when the user needs quantified justification for refactoring work. The purpose is to convert current Code Health into a clear argument about delivery speed and defect reduction.
When to Use
- A user asks for ROI, business value, or management justification.
- The workflow needs evidence to prioritize refactoring work.
- An engineering team needs a short case for why improving a file is worth the effort.
Do not use this skill to explain Code Health fundamentals. Use explaining-code-health for that.
Quick Reference
code_health_refactoring_business_case: Generate modeled outcomes for one file.code_health_score: Optional supporting baseline when the user wants the current score called out separately.
Implementation
- Run
code_health_refactoring_business_casefor the target file. - Present the recommended target scenario.
- Summarize the optimistic and pessimistic outcomes as a bounded range, not a promise.
- Translate the output into a short investment rationale tied to delivery speed and defect reduction.
- If needed, pair the result with
code_health_scoreorcode_health_reviewto show why the file is a refactoring candidate.
Common Mistakes
- Presenting modeled outcomes as guarantees.
- Using this skill for project-wide ranking without first narrowing candidate files.
- Explaining raw JSON instead of converting it into a short business argument.
- Forgetting that the tool is file-scoped.
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.
- 12d ago First seen · 39 lines · 34 tokens per session scan A 5112689dac74
making-the-business-case-for-code-health is a skill published in the GitHub repository DavidVujic/my-eca-config (11 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 343 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…