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/jjcall/vibeship-boilerplateWrote 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/jjcall/vibeship-boilerplate/diagnose)<a href="https://agentmods.dev/rules/jjcall/vibeship-boilerplate/diagnose"><img src="https://agentmods.dev/badge/rules/jjcall/vibeship-boilerplate/diagnose.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.00834 |
| Opus 5 | $0.00000 | $0.00417 |
| Sonnet 5 | $0.00000 | $0.00167 |
| Haiku 4.5 | $0.00000 | $0.00083 |
Grade A, and why
diagnose scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
* **Check Dependencies & External Interactions:** Verify versions and statuses of dependencies. If external systems are involved, use safe commands (`run_terminal_cmd` with `require_user_approval=true` if needed for diag The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 8d ago First seen · 34 lines · 0 tokens per session scan A b39366fb987e
diagnose is a cursor rule published in the GitHub repository jjcall/vibeship-boilerplate (4 stars, last pushed 1y ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 834 tokens. A static security scan graded it A with 1 finding (makes network calls). 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
e2e-testing
E2E Flow Tests setup and debugging guide.
dev-port-allocation
A shared process for assigning development-server ports to different projects and checking that their declarations match the central registry.
quality
Quality assurance standards for security (OWASP), performance, accessibility (WCAG), and code quality reviews.
debug
Bug diagnosis and fixing standards - root cause analysis, minimal fixes, regression tests.
coupling-cohesion
A code-structure guide based on keeping related behavior together and dependencies flowing in clear directions. It covers import cycles, oversized shared files, server boundaries, and repeated decision logic.
vite-doctor
A configuration rule for Vite Doctor, a scanner for Vue, Nuxt, Vite, and Nitro projects that checks for common issues such as routing and security problems.