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/shipkit-io/bonesWrote 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/shipkit-io/bones/single-responsibility-principle)<a href="https://agentmods.dev/rules/shipkit-io/bones/single-responsibility-principle"><img src="https://agentmods.dev/badge/rules/shipkit-io/bones/single-responsibility-principle/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/shipkit-io/bones/single-responsibility-principle"><img src="https://agentmods.dev/badge/rules/shipkit-io/bones/single-responsibility-principle.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.00000 | $0.00707 |
| Opus 5.5 | $0.00000 | $0.00283 |
| Sonnet 5.5 | $0.00000 | $0.00141 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
single-responsibility-principle 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 yesterday.
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
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- yesterday First seen · 110 lines · 0 tokens per session scan A 0d202ca7f2a1
single-responsibility-principle is a cursor rule published in the GitHub repository shipkit-io/bones (21 stars, last pushed yesterday), with no licence file. It costs nothing until one of its globs matches a file; then it loads 707 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-10-14.
Other cursor rules, from other repositories
sync-plate-ui
Sync Plate registry UI into downstream apps with fork-aware comparison, scoped apply and changelog tracking.
verify
Verify Plate packages, browser editor behavior, CLI artifacts, collaboration and tests at their actual owners. Load before selecting, changing or waiving proof, writing tests or claiming a fix works.
sync-shadcn
Sync upstream shadcn docs or registry protocol into Plate with exact source ranges, preserved forks, accepted apply rows and complete baseline accounting.
plate-plugins
Build or change Plate plugins and packages with semantic ownership, inferred contracts, React adapters and package proof. Use for plugin fields, options, serializers and cross-package features.
best-api
Design, review or repair a Plate public call shape using live Slate-based contracts, ideal call sites, inference and ownership.
plate-next
Review or sync a live Plate package, file or API path against the published Slate-based framework and repair accepted findings.