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/danielsmithdevelopment/ClawQLWrote 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/danielsmithdevelopment/clawql/git-no-direct-main-push-without-explicit-user-consent)<a href="https://agentmods.dev/rules/danielsmithdevelopment/clawql/git-no-direct-main-push-without-explicit-user-consent"><img src="https://agentmods.dev/badge/rules/danielsmithdevelopment/clawql/git-no-direct-main-push-without-explicit-user-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/danielsmithdevelopment/clawql/git-no-direct-main-push-without-explicit-user-consent"><img src="https://agentmods.dev/badge/rules/danielsmithdevelopment/clawql/git-no-direct-main-push-without-explicit-user-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.00208 | $0.00208 |
| Opus 5.5 | $0.00083 | $0.00083 |
| Sonnet 5.5 | $0.00042 | $0.00042 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
git-no-direct-main-push-without-explicit-user-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 Safety: No Direct Main Push
- Never run
git pushtomainormasterunless the user explicitly asks for it in the current message. - If the user asks to "commit", "create PR", or "push" without naming a branch, do not push to
main/master; ask which branch/PR flow they want. - Before any push command, print the exact target (
remote,branch) in the chat and require explicit confirmation when target ismain/master. - Prefer branch + PR flow for all agent-authored changes.
Required guard
Before executing a push:
- Run
git rev-parse --abbrev-ref HEAD. - If branch is
mainormasterand there is no explicit same-message user instruction to push main/master, stop and ask. - Never infer consent from prior messages.
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 · 20 lines · 208 tokens per session scan A d09cfde412a3
git-no-direct-main-push-without-explicit-user-consent is a cursor rule published in the GitHub repository danielsmithdevelopment/ClawQL (13 stars, last pushed today), licensed Apache-2.0. It adds 208 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-30.
Other cursor rules, from other repositories
rebase-only-merged-agents
When rebasing after a merge, only rebase the agents whose branches you just merged. Do not rebase agents that are still running.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
git-workflow
Rules for git operations, commit strategy, and GitHub CLI usage.
release-checklist
What to update with each code change or version release.
git-workflow
Git commit format and PR process - conventional commits.
branching-merging-strategy
This is a set of instructions to the AI Assistant for branching and merging strategy.