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/Vimalk0703/shipworthyWrote 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/vimalk0703/shipworthy/cursorrules)<a href="https://agentmods.dev/rules/vimalk0703/shipworthy/cursorrules"><img src="https://agentmods.dev/badge/rules/vimalk0703/shipworthy/cursorrules/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/rules/vimalk0703/shipworthy/cursorrules"><img src="https://agentmods.dev/badge/rules/vimalk0703/shipworthy/cursorrules.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.00866 | $0.00866 |
| Opus 5.5 | $0.00346 | $0.00346 |
| Sonnet 5.5 | $0.00173 | $0.00173 |
| Haiku 4.5 | $0.00087 | $0.00087 |
Grade A, and why
cursorrules 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 1mo 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shipworthy — Production Engineering Guardrails for Cursor
When using this adapter, first output:
⚓ shipworthy › adapter:
cursor— translating Shipworthy skills for Cursor
Is your code worthy of shipping?
Non-Negotiable Defaults
Apply these automatically on every project, every session:
- NEVER use console.log — install and use pino (Node.js), logging (Python), or slog (Go). Even for server startup.
- ALWAYS use Zod for input validation (TypeScript).
npm install zodbefore writing any route. Python: Pydantic. Go: validator. - ALWAYS write tests — Vitest (TS), pytest (Python), stdlib testing (Go). Configure coverage.
- ALWAYS set up ESLint (TS), Ruff (Python), or golangci-lint (Go).
- NEVER use
: any— useunknownand narrow with type guards.catch (err: unknown). - Proper HTTP status codes — 201 create, 204 delete, 400 validation, 401 auth, 403 forbidden, 404 not found.
- ALWAYS use a database — never in-memory arrays. SQLite minimum.
- NEVER hardcode secrets — environment variables, validated at startup.
- Passwords: bcrypt/argon2 — never MD5/SHA/plaintext.
- Safe error messages — never expose stack traces or internal details to clients.
Intent-to-Spec (Before Coding)
For any non-trivial feature request, generate a lightweight spec BEFORE writing code:
- Capture what the user wants (their words), who it's for, and why it matters
- Define concrete deliverables and 3-7 acceptance criteria
- Check constraints from
.shipworthy/architecture.mdif it exists - Save to
.shipworthy/specs/[feature-name].md - For non-technical users: do this silently. For engineers: show for approval.
Skip for quick fixes (typos, config changes, renames).
Project Diagnosis
At the start of each session, mentally check:
- Does
.gitignoreexist and include.env? - Do tests exist?
- Is a linter configured?
- Is CI set up?
- Does
.shipworthy/architecture.mdexist?
If critical gaps exist (especially .env not in .gitignore), flag them before proceeding.
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.
- 1mo ago First seen · 72 lines · 866 tokens per session scan A 721284610b47
cursorrules is a cursor rule published in the GitHub repository Vimalk0703/shipworthy (6 stars, last pushed 6mo ago), licensed MIT. It adds 866 tokens to every session, about $0.0035 per session on Opus 5.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 cursor rules, from other repositories
hedgehog
Hedgehog build discipline — how to work in this repo.
skill-rust-workspace
Decisão e migração de Cargo workspace multi-crate para projetos Rust/Axum. Use durante design/blueprint para decidir o layout, ou quando um projeto single-crate cresceu além do que comporta confortavelmente.
skill-dag-runner
Como construir e executar grafos de tasks (DAG) do método DARE com paralelismo lógico via dare-dag.yaml. O Cursor é o executor; o CLI dare é orquestrador.
skill-fastapi-api
Padrões DARE para APIs REST em Python + FastAPI + Pydantic v2 + SQLAlchemy 2.0 async + alembic. Routers, dependency injection, schemas Pydantic, OAuth2+JWT, slowapi rate limit, pytest+httpx, OpenAPI auto-gerado.
skill-go-gin-api
Padrões DARE para APIs REST em Go + Gin (ou stdlib net/http) + sqlc + PostgreSQL. Handlers, services, repositories, middleware, validação via binding tags, JWT, rate limit, swag OpenAPI, testify + httptest.
skill-layered-design
Layered Design — enforce arquitetura estrita Handler→Service→Repository→Model em todos os projetos DARE, independente de linguagem. Inspirado em "Layered Design for Ruby on Rails Applications" de Vladimir Dementyev (Evil Martians).