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 fabioc-aloha/Alex_Skill_Mall --skill build-script-path-rotgit clone --depth 1 https://github.com/fabioc-aloha/Alex_Skill_MallWrote 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/fabioc-aloha/alex_skill_mall/build-script-path-rot)<a href="https://agentmods.dev/skills/fabioc-aloha/alex_skill_mall/build-script-path-rot"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/build-script-path-rot/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/fabioc-aloha/alex_skill_mall/build-script-path-rot"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/build-script-path-rot.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.00018 | $0.00596 |
| Opus 5 | $0.00009 | $0.00298 |
| Sonnet 5 | $0.00004 | $0.00119 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
build-script-path-rot 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 9d 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.
Build Script Path Rot
The Problem
Hardcoded paths in build scripts break when directory structure changes:
// Bad: hardcoded path
const srcDir = './src/components';
const outDir = './dist/components';
// After restructure: src/components → packages/ui/src
// Script breaks silently or with confusing errors
The Solution
Option 1: Resolve Relative to Manifest
const path = require('path');
const pkg = require('./package.json');
// Paths defined in package.json
const srcDir = path.resolve(__dirname, pkg.directories?.src || 'src');
const outDir = path.resolve(__dirname, pkg.directories?.dist || 'dist');
// package.json
{
"directories": {
"src": "packages/ui/src",
"dist": "dist"
}
}
Option 2: Config File
// build.config.js
module.exports = {
srcDir: './packages/ui/src',
outDir: './dist',
assets: './assets'
};
// build.cjs
const config = require('./build.config.js');
const srcDir = path.resolve(__dirname, config.srcDir);
Option 3: Auto-Discover
// Find src directory by looking for markers
function findSrcDir() {
const candidates = ['src', 'packages/ui/src', 'lib'];
for (const dir of candidates) {
if (fs.existsSync(path.join(dir, 'index.ts'))) {
return dir;
}
}
throw new Error('Could not find source directory');
}
Red Flags
| Pattern | Risk |
|---|---|
'./src/' hardcoded |
Will break on restructure |
process.cwd() + '/src' |
Breaks if script run from different dir |
Relative paths without path.resolve |
Platform-specific issues |
Safe Patterns
// Always resolve from script location
const scriptDir = __dirname;
const projectRoot = path.resolve(scriptDir, '..');
const srcDir = path.resolve(projectRoot, 'src');
// Or from package.json location
const pkgPath = require.resolve('./package.json');
const projectRoot = path.dirname(pkgPath);
Verification
- Move a directory → script still works (reads from config)
- Run script from different working directory → still works
- Paths in config match actual structure
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.
- 9d ago First seen · 113 lines · 18 tokens per session scan A 18f11db6b406
build-script-path-rot is a skill published in the GitHub repository fabioc-aloha/Alex_Skill_Mall (4 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 596 once invoked, about $0.0001 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
apply-fishbone-diagram
Use when investigating the root cause of a quality defect, recurring process failure, or operational problem — to map all contributing causes across multiple categories simultaneously before selecting which cause to address.
apply-early-intervention
Use when you detect early warning signals — technical debt accumulating, customer relationship cooling, team friction forming, process degrading — to intervene while the problem is still small and cheap, because intervention cost increases nonlinearly with delay.
diagnose-battery-charging-problem
Use when a vehicle has starting problems, battery warning lights, or electrical symptoms — systematically testing battery condition, alternator output, and charging circuit integrity to identify the root cause before replacing components.
diagnose-electrical-fault
Use when a vehicle has a blown fuse, inoperative accessory, warning light, or intermittent electrical failure — applying a systematic test sequence (visual, OBD-II codes, voltage/continuity testing) to isolate the fault to a specific component or circuit without replacing parts blindly.
diagnose-brake-system-problem
Use when experiencing brake warning signs such as noise, pulsation, pulling, soft pedal, or brake warning light to identify the fault before driving or seeking repair.
diagnose-check-engine-light
Use when a check engine light is illuminated and you need to identify the fault code, assess severity, and decide next steps.