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/logosdx/monorepo/dogfoodinggit clone --depth 1 https://github.com/logosdx/monorepoWrote 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/logosdx/monorepo/dogfooding)<a href="https://agentmods.dev/rules/logosdx/monorepo/dogfooding"><img src="https://agentmods.dev/badge/rules/logosdx/monorepo/dogfooding.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.00000 | $0.00553 |
| Opus 5 | $0.00000 | $0.00277 |
| Sonnet 5 | $0.00000 | $0.00111 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
dogfooding 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dogfooding Standards
Always use @logosdx/utils throughout the monorepo to validate APIs and demonstrate best practices.
Core Principle
- Fail-prone operations (I/O, network, async) → Use error tuple
[result, error] - Business logic → Return actual results directly
- Never use try-catch → Always use
attempt/attemptSync
Error Handling Patterns
import { attempt, attemptSync } from '@logosdx/utils'
// ✅ Fail-prone operations (I/O, network, async)
const [result, err] = await attempt(() => fetch('/api/users'))
if (err) return handleError(err)
// ✅ Business logic returns actual results
function modifyUserEmail(user: User, newEmail: string): User {
if (!isValidEmail(newEmail)) throw new InvalidEmailError()
return { ...user, email: newEmail }
}
// ✅ Composition
async function updateUserEmail(userId: string, newEmail: string): Promise<User> {
const [user, fetchErr] = await attempt(() => fetchUser(userId))
if (fetchErr) throw fetchErr
const modifiedUser = modifyUserEmail(user, newEmail)
const [, saveErr] = await attempt(() => saveUser(modifiedUser))
if (saveErr) throw saveErr
return modifiedUser
}
Required Utilities
- Error handling:
attempt,attemptSync - Data ops:
clone,equals,merge,reach - Flow control:
debounce,throttle,rateLimit,retry,circuitBreaker,withTimeout,batch - Validation:
assert,assertObject,isObject,isBrowser - Performance:
memoize,memoizeSync,definePrivateProps
Quick Examples
// Error handling
const [result, err] = await attempt(() => fetch('/api'));
if (err) return handleError(err);
// Data operations
const cloned = clone(complexState);
if (!equals(oldState, newState)) triggerUpdate();
// Flow control
const debouncedSearch = debounce(search, 300);
const resilient = retry(circuitBreaker(apiCall), { retries: 3 });
// Business logic (direct return)
function calculateTotal(items: CartItem[]): number {
return items.reduce((sum, item) => sum + item.price * item.quantity, 0);
}
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 · 70 lines · 0 tokens per session scan A 349271528227
dogfooding is a cursor rule published in the GitHub repository logosdx/monorepo (7 stars, last pushed 20d ago), licensed BSD-3-Clause. It costs nothing until one of its globs matches a file; then it loads 553 tokens. 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.