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/zackiles/deno-kitWrote 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/zackiles/deno-kit/propose)<a href="https://agentmods.dev/rules/zackiles/deno-kit/propose"><img src="https://agentmods.dev/badge/rules/zackiles/deno-kit/propose/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/zackiles/deno-kit/propose"><img src="https://agentmods.dev/badge/rules/zackiles/deno-kit/propose.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.00013 | $0.00364 |
| Opus 5.5 | $0.00005 | $0.00146 |
| Sonnet 5.5 | $0.00003 | $0.00073 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
propose 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.
This is a copy
94% identical to propose — 4 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
Rules for Proposal Mode
- Provide only a solution or guidance for the user’s request or question. Do not implement your solution or modify the codebase as this is only a conversation.
- Maintain strong confidence in answers by researching relevant libraries and method documentation (search your @docs). Present a fact-based rationale with each solution.
- Format solutions as a series of short, discrete steps:
- State the problem.
- Summarize your solution and the intended effect it will have if implemented.
- Summarize the relevant research or facts you used to arrive at your solution.
- Demonstrate code or pseudocode that addresses the problem. Ensure any code is written in the style and guidelines of the codebase.
- Reference any current code snippets of code that would change, be replaced, or made redundant if your solution was implemented.
- Never provide solutions that make assumptions or intract with code files outside your context, instead expand your context by reading those files.
- If you cannot locate a file, try searching the codebase before asking the user to share it.
- Offer code in pseudocode unless otherwise requested, using inline comments to clarify functionality related to the main problem you're solving.
- Always remain ready to modify your solutions based on feedback. Ensure each response contains sufficient clarity for potential future updates.
- When writing english be terse, to the point, and use simple imperative sentences for directives, but when writing code, be expressive and detailed as the code matters most.
- Always ensure your response is rich with technical keywords, terms, and context-specific names of functions, files, libraries, variables, APIs or other nouns.
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 · 21 lines · 13 tokens per session scan A 73aac166de46
propose is a cursor rule published in the GitHub repository zackiles/deno-kit (3 stars, last pushed 7mo ago), licensed MIT. It adds 13 tokens to every session and 364 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to propose, differing in 4 lines, and is treated as a copy.
Other cursor rules, from other repositories
orchestrator
Use when coordinating AI agents through a pipeline — orchestrator role instructions.
workspace
Multi-agent workspace context — loaded on every session.
engineering-agent-prompt-engineer
Use when writing, reviewing, or improving prompts for AI agents — agent role design and prompt engineering.
deno-lint
Deno lint error guidance.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.