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/kws-projects/react-boilerplateWrote 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/kws-projects/react-boilerplate/git-workflow)<a href="https://agentmods.dev/rules/kws-projects/react-boilerplate/git-workflow"><img src="https://agentmods.dev/badge/rules/kws-projects/react-boilerplate/git-workflow/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/kws-projects/react-boilerplate/git-workflow"><img src="https://agentmods.dev/badge/rules/kws-projects/react-boilerplate/git-workflow.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.00245 | $0.00245 |
| Opus 5.5 | $0.00098 | $0.00098 |
| Sonnet 5.5 | $0.00049 | $0.00049 |
| Haiku 4.5 | $0.00024 | $0.00024 |
Grade A, and why
git-workflow 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 Workflow
main= production,develop= development.- Branch new work out from
main(e.g.feat/...,fix/...). - Open a PR against the target branch (normally
develop); merge only after review and passing CI. - Never commit directly to
mainordevelop. The single exception is the automated version-bump commit onmain(handled by.github/workflows/release.yml). - Use Conventional Commits (enforced by commitlint). These prefixes directly
control the automated version bump on merge to
main:BREAKING CHANGEor!:→ major bumpfeat:→ minor bumpfix:,chore:,docs:, etc. → patch bump
When asked to "commit" or "push" work, create or use a feature branch and prefer
opening a PR; do not push straight to main/develop. See CONTRIBUTING.md for
the full process.
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 · 24 lines · 245 tokens per session scan A 5de345c8d46f
git-workflow is a cursor rule published in the GitHub repository kws-projects/react-boilerplate (3 stars, last pushed 4mo ago), licensed MIT. It adds 245 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
releasing
How to release AdLoop to PyPI — version bumping, tagging, and publishing.
github-workflow
GitHub invariants — standard flow on listed use cases; no issue spam; tick linked checklists before merge.
git
Git rules. Conventional commits, atomic staging, no force push.
release-ts-sdk
Release @aptos-labs/ts-sdk or @aptos-labs/confidential-asset — version bump, changelog stamp, release PR, then tag + GitHub Release that triggers NPM publish.
40-git-safety
Git safety rule for branches, commits, pushes, and destructive Git commands.
git-master
Git operations — clean commits, PR prep, conflict resolution, change summaries.