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/ratnesh-maurya/cursor-claude-personasWrote 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/ratnesh-maurya/cursor-claude-personas/rules-async-dependencies)<a href="https://agentmods.dev/rules/ratnesh-maurya/cursor-claude-personas/rules-async-dependencies"><img src="https://agentmods.dev/badge/rules/ratnesh-maurya/cursor-claude-personas/rules-async-dependencies/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/ratnesh-maurya/cursor-claude-personas/rules-async-dependencies"><img src="https://agentmods.dev/badge/rules/ratnesh-maurya/cursor-claude-personas/rules-async-dependencies.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.00000 | $0.00214 |
| Opus 5 | $0.00000 | $0.00107 |
| Sonnet 5 | $0.00000 | $0.00043 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
rules--async-dependencies 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.
What it actually says
Dependency-Based Parallelization
For operations with partial dependencies, use better-all to maximize parallelism. It automatically starts each task at the earliest possible moment.
Incorrect (profile waits for config unnecessarily):
const [user, config] = await Promise.all([
fetchUser(),
fetchConfig()
])
const profile = await fetchProfile(user.id)
Correct (config and profile run in parallel):
import { all } from 'better-all'
const { user, config, profile } = await all({
async user() { return fetchUser() },
async config() { return fetchConfig() },
async profile() {
return fetchProfile((await this.$.user).id)
}
})
Reference: https://github.com/shuding/better-all
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 · 37 lines · 0 tokens per session scan A bfd348ab519f
rules--async-dependencies is a cursor rule published in the GitHub repository ratnesh-maurya/cursor-claude-personas (8 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 214 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-09-03.
Other cursor rules, from other repositories
tell-mcp-api
MCP server and web API boundary rules.
backend-conventions
Backend/CLI conventions for cursor-doctor TypeScript modules.
cursorrules
You are an expert backend API developer. Follow these rules strictly for REST APIs, GraphQL servers, and microservices.
1000-rails-general
Follow general Rails 7.2 conventions and patterns.
1001-rails-controllers
Follow Rails 7.2 controller standards and patterns when creating or editing controllers.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.