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 rules/jj-jamen/buildable-plugin-skills/buildablegit clone --depth 1 https://github.com/jj-jamen/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/rules/jj-jamen/buildable-plugin-skills/buildable)<a href="https://agentmods.dev/rules/jj-jamen/buildable-plugin-skills/buildable"><img src="https://agentmods.dev/badge/rules/jj-jamen/buildable-plugin-skills/buildable.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 | $0.00000 | $0.00187 |
| Opus 5 | $0.00000 | $0.00093 |
| Sonnet 5 | $0.00000 | $0.00037 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
buildable 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 3d 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.
This is a copy
100% identical to buildable — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Buildable Cursor Rule
When the user asks to generate a local app prototype, use Buildable's workflow from this local repository. Prefer running buildable plan "<prompt>" first when a concrete app spec would reduce ambiguity.
- Classify the prompt with
core/classifier.md. - Apply
core/ask-vs-build-policy.md. - Generate an app spec with
core/app-spec-schema.md. - Load only the relevant files from
knowledge/andtemplates/. - Build locally with mock/local data by default.
- Review against
knowledge/quality-rubrics/.
Do not add billing, accounts, cloud previews, managed databases, telemetry, hosted deployment, or central template services unless explicitly requested.
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.
- 3d ago First seen · 20 lines · 0 tokens per session scan A 34025c03c68e
buildable is a cursor rule published in the GitHub repository jj-jamen/buildable-plugin-skills (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 187 tokens. A static security scan graded it A with 0 findings. It is 100% identical to buildable, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.