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/jeremydev87/codingbuddy/importsgit clone --depth 1 https://github.com/JeremyDev87/codingbuddyWhat 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.00590 | $0.00590 |
| Opus 5 | $0.00295 | $0.00295 |
| Sonnet 5 | $0.00118 | $0.00118 |
| Haiku 4.5 | $0.00059 | $0.00059 |
Grade A, and why
imports 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 yesterday.
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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
codingbuddy Rules
Workflow
- PLAN → ACT → PLAN (default flow)
- EVAL only on explicit request
- AUTO for autonomous PLAN → ACT → EVAL cycle until quality achieved
Required Actions
When PLAN, ACT, EVAL, AUTO keywords detected → Immediately call parse_mode MCP tool
Context Persistence
After completing work in any mode → call update_context MCP tool to persist decisions and notes.
Quality Tools
analyze_task— Pre-planning task analysis with risk assessmentgenerate_checklist— Contextual checklists for security, accessibility, performancesearch_rules— Search project rules and guidelinesget_code_conventions— Get code conventions and style guide
Core Principles
- TDD: Red → Green → Refactor
- Test coverage 90%+
- TypeScript strict (no
any) - Server Components first
Project Config
Use get_project_config MCP tool to retrieve project-specific settings (language, tech stack, conventions).
Skills
When a skill might apply to the user's task:
- Call
recommend_skillswith the user's prompt - If recommendations returned, call
get_skillwith the top skillName - Follow the loaded skill instructions
Key skill triggers:
- Bug/error/debug →
systematic-debugging - New feature/build →
brainstorming→writing-plans - TDD/test →
test-driven-development - Plan execution →
executing-plans
Detailed Rules
All details in Single Source of Truth:
packages/rules/.ai-rules/rules/augmented-coding.mdpackages/rules/.ai-rules/rules/clarification-guide.mdpackages/rules/.ai-rules/rules/core.mdpackages/rules/.ai-rules/rules/parallel-execution.mdpackages/rules/.ai-rules/rules/project.mdpackages/rules/.ai-rules/rules/structured-reasoning-guide.mdpackages/rules/.ai-rules/agents/README.md
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.
- yesterday First seen · 65 lines · 590 tokens per session scan A cb2c1f07889f
imports is a cursor rule published in the GitHub repository JeremyDev87/codingbuddy (31 stars, last pushed 4mo ago), licensed MIT. It adds 590 tokens to every session, about $0.0030 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-30.
Other cursor rules, from other repositories
open-mercato
Route every standalone app task through the root agent rules.
generated-guard
Prevent edits to generated application registries.
coding-guidelines
React Native Expo SDK 54 project with TypeScript, Expo Router v6, Redux Toolkit, and modern development practices.
webdriver-management
Selenium WebDriver lifecycle management — driver factory, explicit waits, browser options, and teardown.
api-testing
Cypress network interception and API testing patterns (cy.intercept, service mocking, request/response validation).
testing-fundamentals
Core Cypress testing principles — selector strategy, smart waiting, and spec organization. Apply when writing or reviewing Cypress E2E tests.