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 agentmods add commands/suntay44/buildable-plugin-skills/buildable-plangit clone --depth 1 https://github.com/suntay44/buildable-plugin-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/commands/suntay44/buildable-plugin-skills/buildable-plan)<a href="https://agentmods.dev/commands/suntay44/buildable-plugin-skills/buildable-plan"><img src="https://agentmods.dev/badge/commands/suntay44/buildable-plugin-skills/buildable-plan.svg" alt="Measured on agentmods" 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.00000 | $0.00469 |
| Opus 5 | $0.00000 | $0.00234 |
| Sonnet 5 | $0.00000 | $0.00094 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
buildable-plan 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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- buildable-plan — 100% identical, 0 lines differ
What it actually says
Buildable Plan
Classify an app idea and produce a local-first Buildable phase plan and app spec.
Run:
buildable plan "<prompt>" 2>/dev/null || node "${BUILDABLE_ROOT:?Set BUILDABLE_ROOT to your Buildable checkout}/bin/buildable.mjs" plan "<prompt>"
If the user attached or referenced screenshots/files and the local path is available, pass each one as --file <path> or --screenshot <path>. Do not paste large file contents into the prompt.
If the user explicitly wants auth/login/accounts, add --with-auth unless the prompt already names the provider. If the user names a provider, use --with-auth-provider <provider> so it is recorded on the spec and kept behind the auth seam.
If buildable is not globally linked, set BUILDABLE_ROOT to the local Buildable checkout. Then follow appSpec.referenceLoadingContract: do not load all templates, load only appSpec.references, load starter source only for the selected template, and inspect only explicit appSpec.referenceInputs supplied by the user. If appSpec.questionsNeeded is true, ask the listed product-direction or architecture questions before design or generate. If there are no blockers, ask at most one or two appSpec.promptRefinement.optionalQuestions only when they would materially improve the plan; otherwise state the defaults and proceed. For vague business prompts like "I have a restaurant", clarify whether the user wants an informational site/menu, ordering/reservations, or management/inventory first. Summarize archetype, target, stack, selected design system, mock-data approach, phases, screens, key features, optional refinement defaults, and explicit user reference inputs.
End by asking whether the user is satisfied with the plan. If not, keep using Buildable Planner and update the saved .buildable/phase-plan.md/json/toon with the requested revision. If yes, offer the target-appropriate next step: Buildable Web Builder for web or Buildable Mobile Builder for mobile. The builder should read the saved plan/spec, use .buildable/phase-plan.toon as compact agent context when present, load only appSpec.references, and load starter source only for the selected template.
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.
- 6d ago First seen · 18 lines · 0 tokens per session scan A deca60dfb366
buildable-plan is a command published in the GitHub repository suntay44/buildable-plugin-skills (53 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 469 tokens. 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.