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/Flower7C3/tune-tanglerWrote 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/flower7c3/tune-tangler/git-consent)<a href="https://agentmods.dev/rules/flower7c3/tune-tangler/git-consent"><img src="https://agentmods.dev/badge/rules/flower7c3/tune-tangler/git-consent/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/flower7c3/tune-tangler/git-consent"><img src="https://agentmods.dev/badge/rules/flower7c3/tune-tangler/git-consent.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.00253 | $0.00253 |
| Opus 5.5 | $0.00101 | $0.00101 |
| Sonnet 5.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 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
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.
- 1mo 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 4mo ago), licensed MIT. It adds 253 tokens to every session, about $0.0010 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
pre-commit-validation
A pre-commit rule requiring local code checks before creating a Git commit. CI, or continuous integration, is the automated checking system that runs for the project.
commit
Conventional Commits specification and git commit workflow rules.
commit-sponsors
Every git commit message must acknowledge BetterDesk supporters.
commit-message-rules
Rules for writing Git commit messages using Gitmoji, a convention that adds an emoji to show the type of change.
git-commit-push-agent
This rule governs the process of committing and pushing changes to git repositories. It should be applied whenever: (1) The user indicates they want to commit or push changes, (2) The user asks about git commit conventions, (3) The user wants to update or save their work to git, or (4) Any git-related commit and push…
git
Git workflow — commit format, push policy, and PR process.