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.
git clone --depth 1 https://github.com/cartaorobbin/pyramid-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/cartaorobbin/pyramid-mcp/development)<a href="https://agentmods.dev/rules/cartaorobbin/pyramid-mcp/development"><img src="https://agentmods.dev/badge/rules/cartaorobbin/pyramid-mcp/development/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/cartaorobbin/pyramid-mcp/development"><img src="https://agentmods.dev/badge/rules/cartaorobbin/pyramid-mcp/development.svg" alt="Reviewed on agentmods" width="80" 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.08377 | $0.08377 |
| Opus 5.5 | $0.03351 | $0.03351 |
| Sonnet 5.5 | $0.01675 | $0.01675 |
| Haiku 4.5 | $0.00838 | $0.00838 |
Grade A, and why
development 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 2mo 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 — 1,201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Rules
This document outlines the development rules and guidelines for the pyramid-mcp project. Following these rules ensures code quality, maintainability, and effective collaboration.
Core Development Principles
1. Plan Before Coding ⭐
ALWAYS plan before writing any code.
- Think first, code second: Before touching any code, take time to understand the problem and design the solution
- Create a clear plan: Write down what you're going to do, how you're going to do it, and what the expected outcome is
- Consider edge cases: Think through potential issues and how to handle them
- Review existing code: Understand how your changes fit into the existing codebase
- Break down complex tasks: Split large features into smaller, manageable pieces
2. Task Management with Planning Files ⭐
ALWAYS maintain planning files to track what we did.
- Organized structure: Use
planning/directory for all planning files - Active vs Backlog: Use
planning/general.mdfor CURRENT tasks being worked on,planning/backlog.mdfor planned future tasks - Task Flow: Move tasks from
planning/backlog.md→planning/general.md→planning/done.mdas they progress - Focus Management: Keep
planning/general.mdfocused (max 1-3 active task groups) - Create/update files: Before starting any work, document what you plan to do in the appropriate planning file
- Track progress: Update the files as you complete tasks
- Document decisions: Record important decisions and why they were made
- Include completion status: Mark tasks as TODO, IN PROGRESS, DONE, or BLOCKED
- Reference issues/PRs: Link to relevant GitHub issues or pull requests
Code Quality Standards
Pre-Development Checklist
Before starting any development work:
- Read and understand the requirement
- Create or update appropriate planning file with your planned work
- Add new tasks to
planning/backlog.md, move toplanning/general.mdwhen starting active work - Check existing issues and PRs for related work
- Plan your approach and get feedback if needed
- Ensure your development environment is set up (
make install) - Plan test strategy: Identify what tests need to be written/updated
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.
- 2mo ago First seen · 1,201 lines · 8,377 tokens per session scan A e80bcd02dd56
development is a cursor rule published in the GitHub repository cartaorobbin/pyramid-mcp (3 stars, last pushed 11d ago), licensed MIT. It adds 8,377 tokens to every session, about $0.0335 per session on Opus 5.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
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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.