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/aiagentwithdhruv/ai-dev-stackWrote 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/aiagentwithdhruv/ai-dev-stack/60-agents)<a href="https://agentmods.dev/rules/aiagentwithdhruv/ai-dev-stack/60-agents"><img src="https://agentmods.dev/badge/rules/aiagentwithdhruv/ai-dev-stack/60-agents/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/aiagentwithdhruv/ai-dev-stack/60-agents"><img src="https://agentmods.dev/badge/rules/aiagentwithdhruv/ai-dev-stack/60-agents.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.00260 |
| Opus 5.5 | $0.00000 | $0.00104 |
| Sonnet 5.5 | $0.00000 | $0.00052 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
60-agents 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 1mo 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
Agent system architecture:
- Separate planner, executor, tools, memory, state, and evaluation logic.
- Agents must be modular and role-specific where possible.
- Tool calls should be explicit, validated, and logged.
Agent rules:
- Agents must not directly access databases or external APIs unless explicitly designed through a tool layer.
- Prompts must be templated and stored separately from orchestration logic.
- Keep critical business workflows deterministic where possible.
- Add output validation and fallback behavior.
- Use structured schemas for agent outputs in production paths.
- Prefer supervisor/policy logic for multi-agent coordination.
Tooling rules:
- Every tool should have:
- a clear purpose
- input schema
- output schema
- failure behavior
- Tools should be side-effect aware.
- Sensitive tools must enforce auth and authorization checks.
Memory/state rules:
- Separate short-term conversational state from long-term memory.
- Store long-term memory only when product requirements justify it.
- Track provenance for stored memories if relevant.
Do not:
- Let agents perform unrestricted actions.
- Hide tool errors.
- Mix prompt text deeply into service/business code.
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.
- 1mo ago First seen · 37 lines · 0 tokens per session scan A 55f775ff0042
60-agents is a cursor rule published in the GitHub repository aiagentwithdhruv/ai-dev-stack (11 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 260 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-08-31.
Other cursor rules, from other repositories
cursorrules
You are building an AI/ML project with Python. The project uses PyTorch for model training, handles data pipelines with proper validation, tracks experiments systematically, and follows production ML engineering practices. Code is type-hinted, tested, and reproducible.
refactoring
Refactoring: systematic approach, extract/inline, guard clauses, early returns.
cross-tool-config
Cross-tool AI config: what transfers between Cursor, Claude Code, Copilot, Windsurf, Gemini, and Codex.
angular
Angular: signals, standalone components, RxJS patterns.
django
Django: models, views, ORM best practices.
fastapi
FastAPI: Pydantic v2, dependency injection, async.