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/oriolshhh/runware-image-mcp/code-quality-guidelinesgit clone --depth 1 https://github.com/Oriolshhh/runware-image-mcpWrote 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/oriolshhh/runware-image-mcp/code-quality-guidelines)<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/code-quality-guidelines"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/code-quality-guidelines.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.00019 | $0.00765 |
| Opus 5 | $0.00010 | $0.00382 |
| Sonnet 5 | $0.00004 | $0.00153 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
code-quality-guidelines 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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: code-quality-guidelines
Code Quality Guidelines
Purpose
Keep every implementation change understandable, reviewable, and safe to extend. This is the general engineering baseline for all code changes, regardless of language or framework.
When to use it
- Before implementing any non-trivial code change.
- When touching shared utilities, public APIs, core flows, or files that already feel tangled.
- During
/fixwhen a quick patch could create hidden coupling. - During
/reviewto identify maintainability issues that are likely to become defects, not as a style nit checklist.
Instructions
- Start from the existing repository style and architecture. Prefer consistency over personal taste unless the existing pattern is actively unsafe.
- Keep the change cohesive: one reason to change per function/module/component. Split only when it reduces coupling or clarifies ownership.
- Make data flow explicit. Avoid hidden global state, temporal coupling, action-at-a-distance side effects, and "magic" behavior.
- Prefer clear names and small interfaces over comments explaining confusing code. Comments should explain why, constraints, or non-obvious tradeoffs.
- Isolate edge-case handling near the boundary where the edge case enters: parsing, validation, I/O, user input, external services, or persistence.
- Preserve type safety and invariants. Do not widen types, use unchecked casts, or make optional/null states more ambiguous to get a patch through.
- Keep dependencies boring. Do not add a dependency, framework, abstraction, or global helper unless the spec or repeated local need justifies it.
- Make failure behavior deliberate: errors should be actionable, logged or surfaced at the right layer, and not swallowed silently.
- Add or update tests around changed behavior, including at least one regression test for a bug fix and one edge case for new logic when applicable.
- Run the smallest meaningful validation first, then the configured gates.
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.
- 2d ago First seen · 75 lines · 19 tokens per session scan A 19712ea6a9f7
code-quality-guidelines is a cursor rule published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 765 once invoked, about $0.0001 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-09-03.
Other cursor rules, from other repositories
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.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.