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/flower7c3/tune-tangler/git-consentgit clone --depth 1 https://github.com/Flower7C3/tune-tanglerWhat 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.00253 | $0.00253 |
| Opus 5 | $0.00127 | $0.00127 |
| Sonnet 5 | $0.00051 | $0.00051 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
git-consent 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 3d 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
Git
- Do not commit, push, tag, reset, or force-push without explicit user consent (e.g. “make a commit”, “push to origin”, “run git commit”, “zrób commit”). Finishing implementation, closing a task, or proposing a commit message is not consent — ask before any git write if the user did not spell it out.
- Phrases like “make it ready”, “finish”, or “done” are not consent unless they explicitly mention committing or pushing.
- A Conventional Commits message suggestion, “conv commit”, or similar is not consent unless the user clearly authorizes the git write.
- Verbatim consent examples that do authorize the matching action: “zrób commit”, “commit”, “push na origin”, “run git commit”, “push to GitHub”.
- Do not amend commits that have already been pushed to
originunless the user explicitly requests it. - Before non-trivial git operations, show reasonable context (for example
git status).
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.
- 3d ago First seen · 14 lines · 253 tokens per session scan A dc5d10269001
git-consent is a cursor rule published in the GitHub repository Flower7C3/tune-tangler (6 stars, last pushed 3mo ago), licensed MIT. It adds 253 tokens to every session, about $0.0013 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
pre-commit-validation
提交前本地跑与 CI 相同的检查，不等 CI 报错.
git-commit-attribution
Git commits must use the human developer identity only; never Cursor Agent co-authorship.
compose-accessibility
Compose accessibility rules for TalkBack — icons, headings, Canvas, live regions, focus, modals, and attribute preservation.
testing-conventions
Testing conventions — JUnit 4, Kotest property tests, instrumented tests, what to test when.
compose-coroutines
Compose scroll/coroutine patterns — prevent programmatic scroll from being mistaken for user scroll, cancellation-safe flag resets.
ios-viewmodel
ViewModels conform to ObservableObject and expose state via @Published properties.