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/David405/harness-kitWrote 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/david405/harness-kit/no-git-publish-without-approval)<a href="https://agentmods.dev/rules/david405/harness-kit/no-git-publish-without-approval"><img src="https://agentmods.dev/badge/rules/david405/harness-kit/no-git-publish-without-approval/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/david405/harness-kit/no-git-publish-without-approval"><img src="https://agentmods.dev/badge/rules/david405/harness-kit/no-git-publish-without-approval.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.00216 | $0.00216 |
| Opus 5.5 | $0.00086 | $0.00086 |
| Sonnet 5.5 | $0.00043 | $0.00043 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
no-git-publish-without-approval 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 2mo 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 publish gate
Never commit, push, or create/open a pull request without explicit human approval for that specific action.
Not sufficient on their own
- Sprint contract approved
- Feature marked PASS or PENDING_REVIEW
- "approve", "proceed", "looks good", or VERIFY green
- Staging product files after execute
These authorize implementation and staging only. Publishing still requires an explicit ask.
Required before publishing
The human must clearly request the action, e.g. "commit", "commit and push", "open a PR".
When unsure, ask. After verify, review, and stage, report readiness and stop — do not publish.
Allowed without publish approval
git status,git diff,git log(review prep)- Local branch create/checkout when the human confirmed the branch name
- Running tests and linters
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.
- 2mo ago First seen · 32 lines · 216 tokens per session scan A dac33b7f60d4
no-git-publish-without-approval is a cursor rule published in the GitHub repository David405/harness-kit (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 216 tokens to every session, about $0.0009 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
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.