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/iolairus/borderlintWrote 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/iolairus/borderlint/cursor)<a href="https://agentmods.dev/rules/iolairus/borderlint/cursor"><img src="https://agentmods.dev/badge/rules/iolairus/borderlint/cursor/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/iolairus/borderlint/cursor"><img src="https://agentmods.dev/badge/rules/iolairus/borderlint/cursor.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.00334 | $0.00334 |
| Opus 5.5 | $0.00134 | $0.00134 |
| Sonnet 5.5 | $0.00067 | $0.00067 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade A, and why
cursor 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
Before adding any AI SDK import, AI endpoint reference, or model identifier to this codebase
(an openai/anthropic/langchain-style package, a provider URL, a Bedrock/HF/Ollama model
id, an OpenAI-compatible base_url, an LLM endpoint in config or .env):
- Run the border check first. With a project policy:
borderlint scan . --policy residency.json --classification <the project's data class>Otherwise inventory mode:borderlint scan . - If the addition would introduce a flow whose jurisdiction is not
local— or a provider/router that resolves tounknown— say so in the conversation BEFORE committing, naming the provider, its residency jurisdiction, its sovereignty bloc, and (if a model id is involved) its provenance bloc. Let the human decide. - If the flow is accepted, record it with an inline waiver carrying a real justification:
# borderlint: allow <reason>. Unjustified waivers are ignored; waivers cannot override a provider or model deny.
Backstop: the pre-commit hook and the CI SBOM diff gate fail any PR that adds new
non-local AI egress — this rule moves the check to where the decision is made.
Install: save as .cursor/rules/borderlint.mdc in your project.
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 · 25 lines · 334 tokens per session scan A 704c5b6ff094
cursor is a cursor rule published in the GitHub repository iolairus/borderlint (10 stars, last pushed 6d ago), licensed MIT. It adds 334 tokens to every session, about $0.0013 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
legal-advisor
Draft privacy policies, terms of service, disclaimers, and legal notices. Creates GDPR-compliant texts, cookie policies, and data processing agreements.
hatch3r-data-classification
Data classification standards covering PII handling, encryption, retention policies, and regulatory compliance.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.