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/Vedthakar/swamrWrote 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/vedthakar/swamr/swamr-project-rules)<a href="https://agentmods.dev/rules/vedthakar/swamr/swamr-project-rules"><img src="https://agentmods.dev/badge/rules/vedthakar/swamr/swamr-project-rules.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.01680 | $0.01680 |
| Opus 5 | $0.00840 | $0.00840 |
| Sonnet 5 | $0.00336 | $0.00336 |
| Haiku 4.5 | $0.00168 | $0.00168 |
Grade A, and why
swamr-project-rules 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 6d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🐝 Swamr Project Rules
These rules apply to ALL agents operating within this project.
File Organization
src/ # Application source code
├── app/ # Next.js App Router pages
├── components/ # Reusable UI components
│ ├── ui/ # Base design system (shadcn/ui)
│ └── [feature]/ # Feature-specific components
├── lib/ # Shared utilities and helpers
├── hooks/ # Custom React hooks
├── types/ # TypeScript type definitions
├── styles/ # Global styles
└── server/ # Server-only code
├── actions/ # Server Actions
├── db/ # Database queries and schema
└── api/ # API route handlers
supabase/ # Supabase config and migrations
├── migrations/ # SQL migration files
└── seed.sql # Seed data
tests/ # Test files
├── unit/ # Unit tests
├── integration/ # Integration tests
└── e2e/ # Playwright E2E tests
swamr/ # Swarm state
├── brain/ # Obsidian vault — the second brain (tracked in git)
│ ├── 00-project/ # Project overview, architecture, tech stack
│ ├── 01-planning/ # Requirements, task tree, decisions
│ ├── 02-foundation/ # Foundation phase outputs
│ ├── 03-build/ # Build phase task outputs and issues
│ ├── 04-testing/ # Test plans and results
│ ├── 05-hardening/ # Security, perf, a11y, legal reports
│ ├── 06-launch/ # Deploy runbooks and handoff docs
│ └── templates/ # Note templates for agents
├── plan.md # Project plan
├── state.json # Execution state (gitignored)
├── evidence/ # QA screenshots and logs (gitignored)
├── scripts/ # Browser automation scripts (gitignored)
└── config.json # Swarm configuration
Coding Standards (All Agents Must Follow)
- TypeScript everywhere — no
anytypes, strict mode enabled - Functional components — no class components in React
- Server Components by default — only add "use client" when needed
- Error boundaries — wrap route segments with error.tsx
- Loading states — add loading.tsx for async routes
- Environment variables — never hardcode secrets, use
.env.local - Imports — use
@/path alias for project imports - Naming — PascalCase for components, camelCase for functions/variables, kebab-case for files
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.
- 6d ago First seen · 151 lines · 1,680 tokens per session scan A 060e4abec430
swamr-project-rules is a cursor rule published in the GitHub repository Vedthakar/swamr (2 stars, last pushed 2mo ago), licensed MIT. It adds 1,680 tokens to every session, about $0.0084 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.