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/comments)<a href="https://agentmods.dev/rules/git-treeline/cli/comments"><img src="https://agentmods.dev/badge/rules/git-treeline/cli/comments/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/comments"><img src="https://agentmods.dev/badge/rules/git-treeline/cli/comments.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.00196 | $0.00196 |
| Opus 5.5 | $0.00078 | $0.00078 |
| Sonnet 5.5 | $0.00039 | $0.00039 |
| Haiku 4.5 | $0.00020 | $0.00020 |
Grade A, and why
comments 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
Comments
Only add comments that explain why, not what. The code should speak for itself.
Do not write
- Comments that restate the next line (
// Check if nil,// Return the result,// Get the branch) - Comments that narrate control flow (
// Loop through items,// Handle error) - Comments that label obvious variable assignments (
// Create the map)
Do write
- Doc comments on exported types and functions (required by Go convention)
- Non-obvious intent, trade-offs, or constraints the code can't convey
- Section labels in complex multi-branch logic (e.g. XML/YAML manipulation with 3+ branches)
- Magic numbers or offsets that need explanation
Test files
Test comments describing setup steps or scenario intent within a large test function are acceptable — they help navigate long test bodies.
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 · 26 lines · 196 tokens per session scan A b19353be8126
comments is a cursor rule published in the GitHub repository git-treeline/cli (5 stars, last pushed 8d ago), licensed MIT. It adds 196 tokens to every session, about $0.0008 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
gonavi-go
A Go coding rule set for the GoNavi repository, based on common Go style guides and the project's own conventions. It covers file structure, errors, context, concurrency, logging, and tests.
backend
You are an expert in Go, Gin, Gorm, Gen, Cosy (https://cosy.uozi.org/) with a deep understanding of best practices and performance optimization techniques in these technologies.
code-style
Formatting, lint, comments language.
20-testing-generated-and-structure
Testing expectations, generated-file boundaries, and CLI structure contract.
shared-libraries
Shared libraries - condition framework, inventory containers, file-backed DB, itinerary, references.
05-go-helpers
In a module whose go.mod requires x/rkit, use rkit before writing a small helper — and over the standard library when both have it (rkit.Contains not slices.Contains, rkit.Coalesce not cmp.Or, rkit.IntToStr not strconv.Itoa). Task → helper map and edge cases: x/rkit/README.md.