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/git-treeline/cli/pre-release-reviewgit clone --depth 1 https://github.com/git-treeline/cliWhat 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.00012 | $0.00386 |
| Opus 5 | $0.00006 | $0.00193 |
| Sonnet 5 | $0.00002 | $0.00077 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
pre-release-review 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.
What it actually says
Pre-Release Review
Before cutting a release, run this review against all changed files since the last tag.
1. Correctness
- No dead code or unreachable branches
- No silently swallowed errors — log or return every
error - All function parameters are used (no dead params)
- Migrations are idempotent — running twice produces no diff
- Edge cases tested: empty input, nil maps, missing keys, invalid formats
2. Data Safety
- File writes don't destroy existing content (round-trip fidelity)
- String-replace migrations won't match unintended content
- No PII or secrets in logs, templates, or generated files
3. Tests
- Every exported function has at least one test
- Edge-case coverage: invalid input, boundary values, concurrent access
- Migration tests verify both in-memory state AND file-on-disk content
- Idempotency tests: run the operation twice, assert no change on second run
4. DRY / Clean Code
- No copy-paste logic — extract shared helpers
- No unnecessary type conversions (e.g. float64 round-trips for int math)
- Comments explain why, not what
- Docstrings on all exported types and functions
5. CI Gate
make ci # tests + vet + lint must all pass
Only pre-existing lint violations are acceptable. New code must be lint-clean.
6. Docs
- CHANGELOG updated with all user-facing changes
- README reflects new config fields, CLI flags, and behaviors
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 · 12 tokens per session scan A b25aede5401d
pre-release-review is a cursor rule published in the GitHub repository git-treeline/cli (5 stars, last pushed 4d ago), licensed MIT. It adds 12 tokens to every session and 386 once invoked, about $0.0001 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.