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/claire-gong-18/awesome-cursorrulesWrote 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/claire-gong-18/awesome-cursorrules/function-length-and-responsibility)<a href="https://agentmods.dev/rules/claire-gong-18/awesome-cursorrules/function-length-and-responsibility"><img src="https://agentmods.dev/badge/rules/claire-gong-18/awesome-cursorrules/function-length-and-responsibility.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.00080 | $0.00080 |
| Opus 5 | $0.00040 | $0.00040 |
| Sonnet 5 | $0.00016 | $0.00016 |
| Haiku 4.5 | $0.00008 | $0.00008 |
Grade A, and why
function-length-and-responsibility 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.
This is a copy
100% identical to function-length-and-responsibility — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
- Write short functions that only do one thing.
- Follow the single responsibility principle (SRP), which means that a function should have one purpose and perform it effectively.
- If a function becomes too long or complex, consider breaking it into smaller, more manageable functions.
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 · 7 lines · 80 tokens per session scan A 0d0dc02928e4
function-length-and-responsibility is a cursor rule published in the GitHub repository claire-gong-18/awesome-cursorrules (0 stars, last pushed 1y ago), licensed CC0-1.0. It adds 80 tokens to every session, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to function-length-and-responsibility, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
e2e-testing
E2E Flow Tests setup and debugging guide.
hatch3r-dynamic-stack-verification
Runtime-evidence gates for stacks with no static type layer (plain-JS Vue, dynamic persistence) — smoke-mount changed components, dormant-collection-read ratchet, runtime smoke evidence on module-boundary changes; a green lint+build+mock-suite proves a layer, not the system.
debug-issue
When the user reports a bug, an error, or unexpected behavior. Enforces four structured phases — reproduction, failing test, root cause isolation, fix and verify — to stop guess-and-check loops.
系统化调试
A step-by-step method for investigating bugs, failed tests, and unexpected behaviour. It provides a structured way to narrow down the cause instead of guessing.
debugging-and-testing-rules
description: Specifies practices for debugging and testing, including logging, unit tests, and ensuring all tests pass. globs: /.
debugging-and-testing-rules
Specifies practices for debugging and testing, including logging, unit tests, and ensuring all tests pass.