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.
git clone --depth 1 https://github.com/sherpa-sh/Sherpa-ActionWrote 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/commands/sherpa-sh/sherpa-action/detect-build-info)<a href="https://agentmods.dev/commands/sherpa-sh/sherpa-action/detect-build-info"><img src="https://agentmods.dev/badge/commands/sherpa-sh/sherpa-action/detect-build-info/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/commands/sherpa-sh/sherpa-action/detect-build-info"><img src="https://agentmods.dev/badge/commands/sherpa-sh/sherpa-action/detect-build-info.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.00006 | $0.00275 |
| Opus 5 | $0.00003 | $0.00138 |
| Sonnet 5 | $0.00001 | $0.00055 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
detect-build-info 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 11d 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
Detect Build Info
Detect the language, build commands, framework, and other info necessary to build a CI/CD pipeline for the project.
- Install
npm i -g @netlify/build-infoif its not available. - Then detect the json build info by running
build-info path/to/site --rootDir /project/root/dir. Use these user provided paths: "$ARGUMENTS". If no paths are provided, assume you are in the correct path. - If you cannot determine the language, build commands (npm i, npm run build, etc) with #2, read the codebase and make your best guess.
- ALWAYS read the code base to determine the appropriate package manager to use (npm, pnpm, yarn, bun, deno, etc)
- Write the output to the file
.sherpa.sh/build-info.md. Ensure .sherpa.sh is in the root of the repo next to .git folder. Never write anything explicitly referencing netlify into the config. Always include the framework, build commands and the folder where the build command must be run from. - Summarize to the user how this project will get build with the
/Sherpa/buildcommand. - Continue with the original command, if there is one.
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.
- 11d ago First seen · 15 lines · 6 tokens per session scan A 422d0c17f364
detect-build-info is a command published in the GitHub repository sherpa-sh/Sherpa-Action (22 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 6 tokens to every session and 275 once invoked, about $0.0000 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 commands, from other repositories
debug
Systematic debugging with automated investigation and 4-phase methodology. Default: inline evidence gathering and diagnosis. --deep: spawns systematic-debugger agent for full autonomous debugging. Use for errors, stack traces, test failures, or unexpected behavior.
think
Single-problem deep reasoning with the deep-think-partner agent. Use for: debugging complex issues, evaluating tradeoffs, validating logic, or thinking through a specific decision. Example: "/think should I use Redis or PostgreSQL for session storage?".
doctor
Cross-plugin system diagnostics — check installed plugins, hook health, build status, and configuration.
diagnose-runtime
Quickly diagnose runtime performance issues in web applications including freezes, hangs, memory leaks, and slow performance.
lint
Command "lint" from ApexIQ/skillsmith, covering command: /lint, goal, resources and execution plan.
debug
Command "debug" from ApexIQ/skillsmith, covering command: /debug, goal, resources and execution plan.