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/galyarderlabs/galyarder-framework/code-reviewergit clone --depth 1 https://github.com/galyarderlabs/galyarder-frameworkWrote 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/galyarderlabs/galyarder-framework/code-reviewer)<a href="https://agentmods.dev/rules/galyarderlabs/galyarder-framework/code-reviewer"><img src="https://agentmods.dev/badge/rules/galyarderlabs/galyarder-framework/code-reviewer.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 | $0.00034 | $0.00932 |
| Opus 5 | $0.00017 | $0.00466 |
| Sonnet 5 | $0.00007 | $0.00186 |
| Haiku 4.5 | $0.00003 | $0.00093 |
Grade A, and why
code-reviewer 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 5d 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.
This is a copy
77% identical to architect — 245 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
THE Agentic Company Framework GLOBAL PROTOCOLS (MANDATORY)
1. Token Economy: The RTK Prefix
The local environment is optimized with rtk (Rust Token Killer). Always use the rtk prefix for shell commands (e.g., rtk npm test) to minimize token consumption.
- Example:
rtk npm test,rtk git status,rtk ls -la. - Note: Never use raw bash commands unless
rtkis unavailable.
2. Traceability: Linear is Law
No cognitive labor happens outside of a tracked ticket. You operate exclusively within the bounds of a project-scoped issue.
- Project Discovery: Before any work, check if a Linear project exists for the current workspace. If not, CREATE it.
- Issue Creation: ALWAYS create or link an issue WITHIN the specific Linear project. NEVER operate on 'No Project' issues.
- Status: Transition issues to "In Progress" before coding and "Done" after verification.
3. Cognitive Integrity: Scratchpad Reasoning
Before executing any high-impact tool (write_file, replace, run_shell_command), it is standard protocol to output a <scratchpad> block demonstrating your internal reasoning, trade-off analysis, and specific execution plan.
4. Technical Integrity: The industry experts Principles
Combat AI slop through rigid adherence to the four principles of Andrej industry experts:
- Think Before Coding: Don't guess. If uncertain, STOP and ASK. State assumptions explicitly. If ambiguity exists, present multiple interpretationsdon't pick silently. Push back if a simpler approach exists.
- Simplicity First: Implement the minimum code that solves the problem. No speculative abstractions. If 200 lines could be 50, rewrite it. No "configurability" unless requested.
- Surgical Changes: Touch ONLY what is necessary. Every changed line must trace to the request. Don't "improve" adjacent code or refactor things that aren't broken. Remove orphans YOUR changes made, but leave pre-existing dead code (mention it instead).
- Goal-Driven Execution: Define success criteria via tests-first. Loop until verified.
- Multi-step tasks MUST use this syntax:
- [Step] verify: [check]
- [Step] verify: [check]
- Multi-step tasks MUST use this syntax:
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.
- 5d ago First seen · 79 lines · 34 tokens per session scan A 8375a68bc7b0
code-reviewer is a cursor rule published in the GitHub repository galyarderlabs/galyarder-framework (22 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 932 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 77% identical to architect, differing in 245 lines, and is treated as a copy.
Other cursor rules, from other repositories
docs
This file provides guidelines for working with the documentation in the /docs directory.
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.