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/zyrexnn/cybermes/cursorrulesgit clone --depth 1 https://github.com/Zyrexnn/CybermesWhat 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.00472 | $0.00472 |
| Opus 5 | $0.00236 | $0.00236 |
| Sonnet 5 | $0.00094 | $0.00094 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
cursorrules 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 yesterday.
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 — 29 lines — stays where its author put it; the contents beside it link to each section on GitHub.
=============================================================================
Cybermes Coding Standards & Operational Rules (.cursorrules)
=============================================================================
1. PYTHON POC SCRIPTING CONVENTIONS
- Always write clean, self-contained Python 3 scripts for Proof-of-Concept verification.
- Use
requestsorhttpxwith explicittimeout=10on all network requests. - Set a realistic User-Agent header (e.g.,
User-Agent: Cybermes-Security-Auditor/1.0). - Ensure all scripts accept a target URL as a CLI argument (
sys.argv[1]) with fallback to the tested default. - Include proper error handling (
try/except requests.exceptions.RequestException) and colorized status prints. - PoC scripts MUST demonstrate minimal-impact reproduction (e.g. read non-sensitive test fields or trigger benign diffs). NEVER script destructive actions.
2. FILE & PATH NAMING STANDARDS
- Vulnerability reports MUST be placed in
reports/<TARGET_SLUG>/findings/<severity>_<vuln_name>.md. - Use lowercase snake_case for all filenames (e.g.,
high_idor_documents.md,poc_login_bypass.py). - NEVER use square brackets
[...]or special shell characters in file names. - Informational observations, missing security headers, and negative test tables MUST go to
reports/<TARGET_SLUG>/evidence/recon_notes.md, NEVER scattered as individual files infindings/. - Maintain open permissions: all newly created files should have permissions readable by the host user (umask 0002 / 0666).
3. SECRET HYGIENE & CREDENTIAL PROTECTION
- NEVER commit real API keys, bearer tokens, or sensitive client passwords to Git repositories.
- When saving evidence or writing markdown reports, always redact sensitive tokens (e.g.,
Bearer [REDACTED_TEST_TOKEN],password: [REDACTED]). - All environment configurations must read from
.envor system environment variables.
4. REPORT AGGREGATION
- After writing or modifying finding files in
reports/<TARGET_SLUG>/findings/, always execute:aggregate_reports <TARGET_SLUG>to keepSUMMARY.mdandmetadata.jsonsynchronized.
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.
- yesterday First seen · 29 lines · 472 tokens per session scan A a6f3f8bf2604
cursorrules is a cursor rule published in the GitHub repository Zyrexnn/Cybermes (668 stars, last pushed 2d ago), licensed Apache-2.0. It adds 472 tokens to every session, about $0.0024 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-30.
Other cursor rules, from other repositories
typescript-coding-convention
This guide outlines the default-standard coding conventions for TypeScript, based on the Google TypeScript Style Guide, supplemented with best practices from other widely-used TypeScript style guides.
cursorrules
Cursor rule "cursorrules" from H4D3ZS/vscodium-rust, covering kortex context integration, this file is auto-populated by the .aim neural vfs system, project structure, development guidelines and quick start.
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.