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 Endokelp/Should-I-build --skill should-i-buildgit clone --depth 1 https://github.com/Endokelp/Should-I-buildWrote 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/endokelp/should-i-build/should-i-build)<a href="https://agentmods.dev/skills/endokelp/should-i-build/should-i-build"><img src="https://agentmods.dev/badge/skills/endokelp/should-i-build/should-i-build/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/endokelp/should-i-build/should-i-build"><img src="https://agentmods.dev/badge/skills/endokelp/should-i-build/should-i-build.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.00118 | $0.01577 |
| Opus 5 | $0.00059 | $0.00788 |
| Sonnet 5 | $0.00024 | $0.00315 |
| Haiku 4.5 | $0.00012 | $0.00158 |
Grade A, and why
should-i-build 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 9d ago First seen · 167 lines · 118 tokens per session scan A b2d9adc4b3d5
should-i-build is a skill published in the GitHub repository Endokelp/Should-I-build (2 stars, last pushed 13d ago), with no licence file. It adds 118 tokens to every session and 1,577 once invoked, about $0.0006 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
qa/e2e-playwright
A method for writing Playwright end-to-end tests, which automate a browser to verify complete user journeys. It covers setup, reusable page objects, login reuse, API mocking, visual checks, multiple browsers and screen sizes, CI, and debugging.
backend/testing-guide
A guide for writing backend tests: small unit tests, tests that check connected parts such as an API and database, and end-to-end tests that follow a complete user flow.
architect/architecture-design
A guide to planning how a software system is organized, including its major parts, layers, folders, data, and API interfaces.
architect/data-api-design
A guide to designing data models and application programming interfaces (APIs), which are the rules software uses to exchange data.
backend/api-development
A guide to building web APIs, including resource URLs, request validation, consistent responses, error handling, authentication, and security.
brainstorming
A requirements-clarification process for turning a vague idea into a written design brief. It asks business-focused questions about the users, problem, main task, and current situation before technical planning begins.