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/daunteeth/woofi-pro-mcp/code-quality-style-rulegit clone --depth 1 https://github.com/DaunteEth/woofi-pro-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/daunteeth/woofi-pro-mcp/code-quality-style-rule)<a href="https://agentmods.dev/rules/daunteeth/woofi-pro-mcp/code-quality-style-rule"><img src="https://agentmods.dev/badge/rules/daunteeth/woofi-pro-mcp/code-quality-style-rule.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.00233 | $0.00233 |
| Opus 5 | $0.00117 | $0.00117 |
| Sonnet 5 | $0.00047 | $0.00047 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
code-quality-style-rule 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 4d 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
🖋️ Code Quality & Style Rules (TypeScript)
- Follow TypeScript best practices and Airbnb TS style.
- Use type annotations everywhere; avoid
any. Validate inputs via Zod schemas. - Functions ≤50 lines, single-purpose—extract helpers into
src/utils/when needed. - Error handling: always catch and rethrow with context; never swallow errors.
- Imports: group external packages, then absolute imports, then relative—alphabetical within groups.
- Use
async/await; wrap external calls with retries (e.g.p-retry) and log at appropriate levels (INFO,WARN,ERROR). - Linters & Formatters: ESLint + Prettier, hooked into pre-commit (Husky).
- Rule file name:
code-quality-style-rule.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.
- 4d ago First seen · 16 lines · 233 tokens per session scan A df2002aee1cd
code-quality-style-rule is a cursor rule published in the GitHub repository DaunteEth/woofi-pro-mcp (1 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 233 tokens to every session, about $0.0012 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
development-conventions
Development conventions, code style, and best practices for the Kaneo project.
ts
Cursor rule "ts" from un-pany/v3-admin-vite, covering ts 开发规范, 类型, 命名, 代码组织 and 错误处理.
app_feature_first_architecture
Feature-first architecture is a design pattern that organizes code by business features rather than technical layers. This approach promotes better maintainability, scalability, and team collaboration by keeping related functionality together and reducing coupling between different parts of the application.
bundling
The project uses a custom type bundling system to provide full TypeScript IntelliSense support in the Monaco editor for @bubblelab/bubble-core and its dependencies. This is necessary because Monaco cannot directly resolve workspace packages or external dependencies.
best_practices
Advanced Best Practices covering Error Handling, Environment Variables, Performance, and Accessibility rules.
typescript-patterns
TypeScript patterns for code organization, classes, types, and symbols as it relates to this project.