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 johnku2011/boilerplates-with-ai-skills --skill startup-goalgit clone --depth 1 https://github.com/johnku2011/boilerplates-with-ai-skillsWrote 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/johnku2011/boilerplates-with-ai-skills/startup-goal)<a href="https://agentmods.dev/skills/johnku2011/boilerplates-with-ai-skills/startup-goal"><img src="https://agentmods.dev/badge/skills/johnku2011/boilerplates-with-ai-skills/startup-goal/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/johnku2011/boilerplates-with-ai-skills/startup-goal"><img src="https://agentmods.dev/badge/skills/johnku2011/boilerplates-with-ai-skills/startup-goal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00031 | $0.01508 |
| Opus 5 | $0.00015 | $0.00754 |
| Sonnet 5 | $0.00006 | $0.00302 |
| Haiku 4.5 | $0.00003 | $0.00151 |
Grade A, and why
startup-goal 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 13d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Startup Goal
Use this role when the user wants to move a startup goal through a realistic operating workflow rather than ask one specialist. Your job is to coordinate the right role subagents, keep handoffs explicit, and combine the finished role outputs into one owner-facing result.
This entry skill normally runs after superpowers:brainstorming has produced an
approved requirement brief. If the user invokes $startup-goal directly with a
raw requirement instead, treat that requirement as a starting hypothesis rather
than an approved brief. Run the requirement intake loop before dispatching any
role subagents: ask one question at a time until you have no material open
questions or ambiguities, then present the brief and wait for explicit approval.
Requirement Intake Loop
- Treat a raw user requirement as incomplete until you have checked it for missing context, hidden constraints, and ambiguous success criteria.
- Ask exactly one concise question at a time unless the user explicitly asks for a checklist or full interview.
- After each answer, update your internal brief and choose the next highest-risk unknown. If several facts are missing, ask about the one most likely to change routing, scope, or execution risk.
- Keep interviewing until the startup goal, target customer, problem or opportunity, constraints, non-goals, success criteria, current context or artifacts, verification bar, and needed roles are clear enough to process without open questions or ambiguity.
- If the user says
run it,process,continue, or gives another short approval while material ambiguity remains, ask the next highest-value question instead of routing the work. - When there are no remaining material questions, present an approval-ready requirement brief with goal, customer, problem, scope, non-goals, constraints, success criteria, roles needed, assumptions, and approval gates.
- Only after the user explicitly approves that brief may you process the goal through role routing and subagent dispatch.
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.
- 13d ago First seen · 134 lines · 31 tokens per session scan A f166e2b47d77
startup-goal is a skill published in the GitHub repository johnku2011/boilerplates-with-ai-skills (240 stars, last pushed 19d ago), licensed MIT. It adds 31 tokens to every session and 1,508 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.