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/pisberg/vibetags/com-example-utils-strictutilitygit clone --depth 1 https://github.com/PIsberg/vibetagsWhat 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.00114 |
| Opus 5 | $0.00000 | $0.00057 |
| Sonnet 5 | $0.00000 | $0.00023 |
| Haiku 4.5 | $0.00000 | $0.00011 |
Grade A, and why
com-example-utils-StrictUtility 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 2d 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.
What it actually says
Rules for StrictUtility
Strict Classpath Integrity
- Rule: Prohibit dynamic class loading, custom classloaders, runtime reflection hacks, or execution of dynamic external code.
- Reason: Runs inside the locked-down payment sandbox where the SecurityManager forbids reflection and custom classloaders; dynamic loading throws at runtime
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.
- 2d ago First seen · 14 lines · 0 tokens per session scan A fd505a3bda5f
com-example-utils-StrictUtility is a cursor rule published in the GitHub repository PIsberg/vibetags (14 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 114 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 cursor rules, from other repositories
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
002-verify-before-act
Requires Claude to read before writing, verify before installing, and confirm before destructive operations.
clarify-first-prompting
Clarify-first strategy: detect ambiguity, ask targeted questions, expand simple prompts into detailed specifications.
design-patterns
Design patterns (GoF) and file size conventions for sweagent TypeScript codebase.
database
Cursor rule "database" from ItamarZand88/awesome-agent-conventions, covering database best practices, prisma setup, prisma models, prisma queries and supabase setup.
080-creative-phase-metrics
description: WHEN entering a creative phase ENSURE comprehensive exploration and validation globs: ["/.md", "/.mdc"] alwaysApply: true.