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/cartaorobbin/pyramid-mcp/tools-and-setupgit 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/tools-and-setup)<a href="https://agentmods.dev/rules/cartaorobbin/pyramid-mcp/tools-and-setup"><img src="https://agentmods.dev/badge/rules/cartaorobbin/pyramid-mcp/tools-and-setup.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.02336 | $0.02336 |
| Opus 5 | $0.01168 | $0.01168 |
| Sonnet 5 | $0.00467 | $0.00467 |
| Haiku 4.5 | $0.00234 | $0.00234 |
Grade A, and why
tools-and-setup 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.
How it starts
The opening of the file, as written. The whole thing — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Environment Setup Rules
This document outlines the development environment setup rules for the pyramid-mcp project. We support two primary development environments: local development with direnv + pyenv and devcontainer development.
⚡ Quick Start (Recommended)
For most developers, this is all you need:
# 1. Clone the repository and navigate to it
cd pyramid-mcp
# 2. Run our battle-tested setup script
make setup-local-env
# 3. Allow direnv to activate the environment
direnv allow
# 4. Verify everything works
make test
That's it! Our automated setup handles everything: Python version validation, virtual environment creation, Poetry installation, dependency management, and pre-commit hooks.
🏆 Battle-Tested Success Record
Our setup has been tested multiple times from scratch with identical results:
- ✅ 3x Complete Clean Installs: Deleted virtual environment and recreated from zero
- ✅ 253/260 Tests Pass: Identical test results across all setups (5 known project-specific failures)
- ✅ 70+ Dependencies: All dev dependencies install correctly every time
- ✅ Full Tool Chain: Python 3.10.15, Poetry 2.1.3, pre-commit hooks, all working
- ✅ Zero Regressions: No functionality lost during standardization
- ✅ 22-Line .envrc: Simplified from 77 lines (71% complexity reduction!)
Proven reliable setup with reproducible results! 🎯
Environment Options
Option 1: Local Development (Recommended for most developers)
- Use when: You want full control over your environment and faster iteration
- Requirements: pyenv, direnv, poetry
- Pros: Fast, flexible, native performance
- Cons: Requires local tool installation and configuration
Option 2: Devcontainer Development
- Use when: You want consistent environments across team members or have limited local setup options
- Requirements: Docker, VS Code with devcontainer extension
- Pros: Consistent, isolated, minimal local setup
- Cons: Slightly slower, requires Docker knowledge
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 · 302 lines · 2,336 tokens per session scan A af23ff7e74ab
tools-and-setup is a cursor rule published in the GitHub repository cartaorobbin/pyramid-mcp (3 stars, last pushed 10mo ago), licensed MIT. It adds 2,336 tokens to every session, about $0.0117 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.
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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.