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/canblmz1/ruleProbWrote 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/canblmz1/ruleprob/main)<a href="https://agentmods.dev/rules/canblmz1/ruleprob/main"><img src="https://agentmods.dev/badge/rules/canblmz1/ruleprob/main/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/canblmz1/ruleprob/main"><img src="https://agentmods.dev/badge/rules/canblmz1/ruleprob/main.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.00137 |
| Opus 5.5 | $0.00000 | $0.00055 |
| Sonnet 5.5 | $0.00000 | $0.00027 |
| Haiku 4.5 | $0.00000 | $0.00014 |
Grade A, and why
main 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.
What it actually says
Coding Rules
Package Manager
- ALWAYS use pnpm. Never use npm or yarn.
TypeScript
- Never use
anytype. Useunknownor explicit types. - Never leave
console.login production code. Use the project logger.
File Safety
- Never modify files under
src/generated/. - Never modify
.envor.env.*files directly.
Commands
- ALWAYS run
pnpm typecheckbefore finishing. - NEVER run
git push --force.
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 · 22 lines · 0 tokens per session scan A 55e0cfc90502
main is a cursor rule published in the GitHub repository canblmz1/ruleProb (7 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 137 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-31.
Other cursor rules, from other repositories
react
React component conventions.
project
Core project context for ai-context-kit.
project
Project conventions - canonical source is AGENTS.md.
cursorrules
DeepInit projection provenance (R3) stage: EMIT → PROJECT (cursor) runid: run-2026-06-13-kemal-e2e source: AGENTS.md (lean tier) — deterministic projection, no new findings note: content inside the DEEPINIT markers is owned + regenerated; edit OUTSIDE them. -->.
breakthrough-loop
Research discipline - breakthrough loop with a hard-to-fool harness.
orchestrator-main
Rules for the main orchestrator agent in multi-agent workflows.