quality-security

A set of Compozy development rules covering security, performance, and code quality, including Go linter requirements.

In plain words
What is it for?
Use it when reviewing or writing Compozy code, especially Go code that handles credentials, external input, HTTP responses, and static-analysis checks.
Why use it?
It helps prevent exposed secrets, unchecked inputs, resource mistakes, inefficient code, and common lint problems.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/compozy/gograph/quality-security
Clone the repo
git clone --depth 1 https://github.com/compozy/gograph

Made for: Cursor.

Per session 310 This file is loaded in full into every session.
When invoked 310 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00310 $0.00310
Opus 5 $0.00155 $0.00155
Sonnet 5 $0.00062 $0.00062
Haiku 4.5 $0.00031 $0.00031

Measured 2d ago against content hash d423c1aff2a6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

quality-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 2d 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.

.cursor/rules/quality-security.mdc · 41 lines

What it actually says

Quality and Security Standards

Security

<security_requirements type="critical">

  • NEVER commit API keys or secrets - use environment variables
  • NEVER expose secrets in logs - use structured logging without sensitive data
  • Handle redaction markers: [REDACTED:amp-token] indicates removed secrets - do not overwrite with markers
  • Use the gosec linter to identify security issues
  • Validate all inputs, especially those from external sources
  • Follow secure coding practices for authentication and authorization </security_requirements>

Performance

<performance_guidelines>

  • Minimize allocations in hot paths
  • Consider resource usage and efficiency </performance_guidelines>

Specific Linter Rules to Follow

<linter_rules type="mandatory">

  • bodyclose: Always close HTTP response bodies
  • errcheck: Check error returns from all function calls
  • goconst: Extract repeated string literals into constants
  • gocritic: Follow idiomatic Go practices
  • staticcheck: Address all static analysis warnings
  • unused: Remove unused code
  • whitespace: Maintain consistent whitespace </linter_rules>
Changes

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.

  1. 2d ago First seen · 41 lines · 310 tokens per session scan A d423c1aff2a6

Subscribe to this mod's changes

quality-security is a cursor rule published in the GitHub repository compozy/gograph (9 stars, last pushed 1y ago), licensed MIT. It adds 310 tokens to every session, about $0.0015 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.