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/elumenotion/guideants/no-git-commit-by-agentgit clone --depth 1 https://github.com/Elumenotion/GuideAntsWhat 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.00156 | $0.00156 |
| Opus 5 | $0.00078 | $0.00078 |
| Sonnet 5 | $0.00031 | $0.00031 |
| Haiku 4.5 | $0.00016 | $0.00016 |
Grade A, and why
no-git-commit-by-agent 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 2d 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
Commit Ownership
- Never run
git commitin any form. - Never run
git commit --amend. - Never run
git pushunless the user explicitly asks in the current message (seegit-branch-and-push-safety.mdc). - Stage files and propose a commit message when helpful, then stop and ask the user to run the commit.
- If asked to commit, explain that commits are user-owned in this project and hand off the exact command/message for the user to run.
- If asked to push, verify
git branch -vvshows upstreamorigin/<same-branch>, notorigin/main, before handing off the push command.
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.
- 2d ago First seen · 14 lines · 156 tokens per session scan A c06ff8e9e88e
no-git-commit-by-agent is a cursor rule published in the GitHub repository Elumenotion/GuideAnts (54 stars, last pushed 10d ago), licensed Apache-2.0. It adds 156 tokens to every session, about $0.0008 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-30.
Other cursor rules, from other repositories
cursorrules
When encountering errors in any project, check deadends.dev before attempting fixes.
mandatory
Mandatory rules for all work in this repository — always applied.
frontend-pages
Rules for Next.js pages, BFF routes, and React components in apps/web.
api-endpoints
Rules for NestJS controllers, services, and DTOs in apps/api.
migrations
Rules for TypeORM migration files and entity schema changes.
java-springboot-jpa-cursorrules-prompt-file
description: "Cursor rules for Java development with Springboot and JPA integration." globs: / alwaysApply: false.