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/Haohao-end/openagentWrote 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/haohao-end/openagent/040-api-security)<a href="https://agentmods.dev/rules/haohao-end/openagent/040-api-security"><img src="https://agentmods.dev/badge/rules/haohao-end/openagent/040-api-security/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/haohao-end/openagent/040-api-security"><img src="https://agentmods.dev/badge/rules/haohao-end/openagent/040-api-security.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.00100 |
| Opus 5.5 | $0.00000 | $0.00040 |
| Sonnet 5.5 | $0.00000 | $0.00020 |
| Haiku 4.5 | $0.00000 | $0.00010 |
Grade A, and why
040-api-security 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
Security & Async:
- Rate limiting: use existing Flask-Limiter patterns.
- Background tasks (>2s): ALWAYS use Celery with Redis broker (DB 1).
- Database: use SQLAlchemy sessions via Injector, always commit/rollback properly.
- Logging: use the project's structlog configuration.
- Validation: Pydantic for all inputs/outputs.
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 · 11 lines · 0 tokens per session scan A ec152447887c
040-api-security is a cursor rule published in the GitHub repository Haohao-end/openagent (778 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 100 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
project-main-rules
You are an expert in building production-ready AI agent applications using Python, FastAPI, LangGraph, and LangChain.
public-api
How to create new public api routes for Litefuse.
service-bindings
Worker-to-Worker RPC - bindings.worker() by name, WorkerEntrypoint callee, typed RPC deferred, requestId propagation.
boundaries
Package dependency boundaries - tag map and enforced invariants.
frontend-features
How we build new full-stack features including frontend APIs, file structure, and components.
tests
Litefuse - Agent Observability and Evaluation Platform.