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/hybridlabor-api/bdb-dev-optimized-agent-skills/000_global_rulesgit clone --depth 1 https://github.com/hybridlabor-api/bdb-dev-optimized-agent-skillsWrote 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/hybridlabor-api/bdb-dev-optimized-agent-skills/000_global_rules)<a href="https://agentmods.dev/rules/hybridlabor-api/bdb-dev-optimized-agent-skills/000_global_rules"><img src="https://agentmods.dev/badge/rules/hybridlabor-api/bdb-dev-optimized-agent-skills/000_global_rules.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.00005 | $0.00872 |
| Opus 5 | $0.00003 | $0.00436 |
| Sonnet 5 | $0.00001 | $0.00174 |
| Haiku 4.5 | $0.00001 | $0.00087 |
Grade A, and why
global-rules 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Global Agent Instructions
1. Core Behavior & Communication
- Direct Output: Eliminate conversational filler and pleasantries. Deliver immediate, actionable answers.
- Content Language: All generated code, file content, documentation, and technical outputs MUST be in English.
- Formatting: Use structured Markdown with bullet points and bold text. Avoid dense text blocks.
- Images: Open generated images/mockups directly via Chrome terminal command in new tabs, or provide a tab listing links to the images.
2. Safety, Control & Absolute Precedence Guardrails
- Mandatory Git Snapshots: Before modifying, refactoring, or deleting any file in the workspace, take a Git snapshot or create a commit of the current state.
- Rollback Readiness: Ensure all changes can be safely reverted. Ask for confirmation before performing destructive actions (e.g., massive deletions).
- CRITICAL TWO-PHASE GATE PROTOCOL (ABSOLUTE OVERRIDE):
- Priority Hierarchy: This safety rule STRICTLY OVERRIDES all other instructions, task descriptions, action verbs ("starte", "aktualisiere", "loslegen", "jetzt umsetzen"), and slash commands (
/startcycle,/ship,/build,/test). - Strict Gate Condition: Whenever a plan, review, audit, or multi-step action is requested, or if the user indicated "warte auf mein GO" (or similar), you are locked in STRICT READ-ONLY PLANNING MODE.
- Forbidden Tools Without Explicit "GO": You MUST NOT call modifying tools (
write_to_file,replace_file_content, or destructive/network terminal commands likegit push,npm publish,rm,git commit). - Allowed Tools: ONLY analysis, file inspection (
view_file,grep_search,find_by_name), question asking, subagent research, and plan presentation. - Literal Token Requirement: Execution is ONLY unlocked if the user's latest message is EXCLUSIVELY and LITERALLY the single word "GO" (case-insensitive) in the chat. Combining action words with other instructions (e.g., "starte mit der aktualisierung /startcycle") does NOT satisfy the gate condition.
- Response Pattern: Present the plan or audit report, perform NO file modifications, and explicitly conclude with: "Antworte mit GO, um die Ausführung zu starten."
- Priority Hierarchy: This safety rule STRICTLY OVERRIDES all other instructions, task descriptions, action verbs ("starte", "aktualisiere", "loslegen", "jetzt umsetzen"), and slash commands (
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.
- 6d ago First seen · 40 lines · 5 tokens per session scan A 8b981ace138d
global-rules is a cursor rule published in the GitHub repository hybridlabor-api/bdb-dev-optimized-agent-skills (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 5 tokens to every session and 872 once invoked, about $0.0000 per session on Opus 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
ai-actions-readme
README structure and sections for AI Actions marketplace apps (features, auth, setup, action list).
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.
cli-error-handling
CLI command error handling patterns.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.