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.
npx agentmods add rules/zackiles/deno-kit/create-releasegit clone --depth 1 https://github.com/zackiles/deno-kitWhat 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 | $0.00009 | $0.00775 |
| Opus 5 | $0.00005 | $0.00387 |
| Sonnet 5 | $0.00002 | $0.00155 |
| Haiku 4.5 | $0.00001 | $0.00077 |
Grade A, and why
create-release 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task
You will analyze the codebase and plan how to release or publish a new version of this package or module, and then execute that plan. To do so, you will follow all of the steps bellow.
Steps
Analyze Codebase
- Run
gitcommands to understand which branch is checked out, whether the main branch is namedmainormaster, if the working directory is clean or has uncommitted changes, how far ahead or behind we are frommain, and what the local git config/custom git options are. - If GitHub info is accessible (via CLI or other tools), check whether there is an open pull request for this branch and how local commits diverge from the remote repository.
- Look in
.github/workflowsto see which release steps occur locally vs remotely (e.g., GitHub Actions). - Grep for package files (
deno.json,deno.jsonc,package.json,package.jsonc,jsr.json,jsr.jsonc) to identify package name, version, publish registries, and any release tools (semantic-release, changesets, husky). - Inspect
.git/hooks to find any configured release processes or commit checks. - Grep for markdown documents (
README.md,AI-README.md,CONTRIBUTING.md,AI-CONTRIBUTING.md,CONTRIBUTORS.md,AI-CONTRIBUTORS.md,CHANGELOG.md,AI-CHANGELOG.md) that may contain instructions for releasing/publishing. - Compare the local version to the latest published version on any registry this package uses.
- Check the latest GitHub tag/release to see if it’s ahead or behind the local version.
Plan the Steps Needed to Release
- Determine if you’re on
mainor a feature branch; if on a feature branch, confirm whether it already exists on the remote. - Check for unstaged changes and stage them if necessary.
- If behind
main, decide whether to fetch and rebase or merge. - Commit any uncommitted changes using a format consistent with the codebase’s commit-message rules (fallback is
@create-commit-message.mdcif unknown). - If a version bump is required, confirm where (e.g., package file) and when (before or after any new commit).
- On the main branch, you may need to push tags to trigger a release or push the feature branch for a pull request if you’re not on main.
- Distinguish which tasks should happen locally vs which are automated by CI/CD or GitHub Actions.
- If conflicting info or uncertainty arises, stop to ask the user for direction.
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.
- yesterday First seen · 43 lines · 9 tokens per session scan A 1de7b1537ba6
create-release is a cursor rule published in the GitHub repository zackiles/deno-kit (3 stars, last pushed 5mo ago), licensed MIT. It adds 9 tokens to every session and 775 once invoked, about $0.0000 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-31.
Other cursor rules, from other repositories
development-conventions
Development conventions, code style, and best practices for the Kaneo project.
docs
This file provides guidelines for working with the documentation in the /docs directory.
architecture
Architecture of openapi-to-cli (ocli).
architecture-constraints
GolemBot architecture hard constraints — must check before modifying any src/ code.
app_feature_first_architecture
Feature-first architecture is a design pattern that organizes code by business features rather than technical layers. This approach promotes better maintainability, scalability, and team collaboration by keeping related functionality together and reducing coupling between different parts of the application.
best_practices
Advanced Best Practices covering Error Handling, Environment Variables, Performance, and Accessibility rules.