Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/tantodefi/xmtpauthnpx agentmods add rules/tantodefi/xmtpauth/monorepo-guidelinesWrote 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/tantodefi/xmtpauth/monorepo-guidelines)<a href="https://agentmods.dev/rules/tantodefi/xmtpauth/monorepo-guidelines"><img src="https://agentmods.dev/badge/rules/tantodefi/xmtpauth/monorepo-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.00455 | $0.00455 |
| Opus 5 | $0.00228 | $0.00228 |
| Sonnet 5 | $0.00091 | $0.00091 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
monorepo-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 7d 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.
What it actually says
Working with XMTP agents in this monorepo
This is the monorepo for XMTP agents. It contains many examples of agents on XMTP.
Required tools
- Node.js v20 or later
- Yarn v4.6.0 (package manager)
- Docker (for local network testing)
Package configuration
When creating new agent examples in this monorepo, follow these guidelines for consistent package.json configuration:
{
"name": "@examples/xmtp-agent-name",
"version": "0.0.1",
"private": true,
"type": "module",
"scripts": {
"build": "tsc",
"dev": "tsx --watch index.ts",
"gen:keys": "tsx ../../scripts/generateKeys.ts",
"lint": "cd ../.. && yarn eslint examples/xmtp-agent-name",
"start": "tsx index.ts"
},
"dependencies": {
"@xmtp/node-sdk": "*" // Inherit the version from the root package.json
/* other dependencies */
},
"devDependencies": {
"tsx": "*",
"typescript": "*"
},
"engines": {
"node": ">=20"
}
}
Note: Ensure the script paths match your actual file structure. Some agents use
index.tsin the root folder while others might usesrc/index.ts.
Environment variables
Your agent will typically require these environment variables in a .env file:
# Network: local, dev, or production
XMTP_ENV=dev
# Private keys (generate with yarn gen:keys)
WALLET_KEY=your_private_key_here
ENCRYPTION_KEY=your_encryption_key_here
Running an agent
Direct execution (recommended for development)
# Navigate to your agent directory
cd examples/your-agent-name
# Install dependencies if needed
yarn install
# Generate keys if you don't have them
yarn gen:keys
# Start the agent with hot-reloading
yarn dev
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.
- 7d ago First seen · 79 lines · 455 tokens per session scan A f0dc15ab3a8f
monorepo-guidelines is a cursor rule published in the GitHub repository tantodefi/xmtpauth (3 stars, last pushed 12mo ago), licensed MIT. It adds 455 tokens to every session, about $0.0023 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-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.