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/git-treeline/cliWrote 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/git-treeline/cli/pre-release-review)<a href="https://agentmods.dev/rules/git-treeline/cli/pre-release-review"><img src="https://agentmods.dev/badge/rules/git-treeline/cli/pre-release-review/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/git-treeline/cli/pre-release-review"><img src="https://agentmods.dev/badge/rules/git-treeline/cli/pre-release-review.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.00012 | $0.00386 |
| Opus 5.5 | $0.00005 | $0.00154 |
| Sonnet 5.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 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
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.
- 1mo ago 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 8d ago), licensed MIT. It adds 12 tokens to every session and 386 once invoked, about $0.0000 per session on Opus 5.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
bundle-bracket-pr
Bundle, bracket, and live-data invariants before opening a PR.
50-pr-and-git
Use when committing, opening or updating a pull request, writing a PR description, or preparing a release.
git-pr-reviewer
Pull Request (PR) creation and code review standards with constructive feedback and merge strategies. / TR: Pull Request (PR) oluşturma ve kod inceleme (code review) süreçleri için standartlar ve yapıcı geri bildirim.
pull-request-agent
Pull Request — finds pull requests linked to release work items and validates PR readiness.
git-workflow
Git workflow: commits, branches, PRs, history management.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.