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/zhimaAi/ChatClawWrote 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/zhimaai/chatclaw/backend-architecture-and-conventions)<a href="https://agentmods.dev/rules/zhimaai/chatclaw/backend-architecture-and-conventions"><img src="https://agentmods.dev/badge/rules/zhimaai/chatclaw/backend-architecture-and-conventions/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/zhimaai/chatclaw/backend-architecture-and-conventions"><img src="https://agentmods.dev/badge/rules/zhimaai/chatclaw/backend-architecture-and-conventions.svg" alt="Reviewed on agentmods" width="80" 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.00014 | $0.02380 |
| Opus 5 | $0.00007 | $0.01190 |
| Sonnet 5 | $0.00003 | $0.00476 |
| Haiku 4.5 | $0.00001 | $0.00238 |
Grade A, and why
backend-architecture-and-conventions 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 9d 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 9d ago First seen · 195 lines · 14 tokens per session scan A cd893c16e846
backend-architecture-and-conventions is a cursor rule published in the GitHub repository zhimaAi/ChatClaw (307 stars, last pushed 3mo ago), licensed GPL-3.0. It adds 14 tokens to every session and 2,380 once invoked, about $0.0001 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
kotlin-springboot-rules
A set of coding rules for Kotlin applications built with Spring Boot, a Java-based framework for web services. It covers project layout, naming, Kotlin style, and common design patterns.
springboot-jpa-best-practices
A set of Chinese-language rules for structuring Java Spring Boot applications that use JPA, a library for database access.
nestjs-general-guidelines
A set of guidelines for NestJS, a Node.js framework for building server applications. It defines how to organize modules, controllers, services, data models, validation, persistence, and tests.
llm-integration-rules
A set of rules for connecting an application to a large language model, including Python wrappers, API endpoints, asynchronous calls, retries, and key management.
data-fetching-rules-for-server-components
A set of rules for fetching data inside Next.js 14 server components, which render on the server rather than in the browser.
dto-conventions
A set of rules for data transfer objects, or DTOs—small structures used to carry data into or out of an application. It requires record types and validation in their compact constructors.