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/benyue1978/solo-flow-mcpWrote 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/benyue1978/solo-flow-mcp/git_commit)<a href="https://agentmods.dev/rules/benyue1978/solo-flow-mcp/git_commit"><img src="https://agentmods.dev/badge/rules/benyue1978/solo-flow-mcp/git_commit/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/benyue1978/solo-flow-mcp/git_commit"><img src="https://agentmods.dev/badge/rules/benyue1978/solo-flow-mcp/git_commit.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.00003 | $0.00213 |
| Opus 5.5 | $0.00001 | $0.00085 |
| Sonnet 5.5 | $0.00001 | $0.00043 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
git_commit 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 Usage
-
Use the following prefixes for commit messages, followed by a colon and a space:
fix— for bug fixesfeat— for new featuresperf— for performance improvementsdocs— for documentation changesstyle— for formatting changesrefactor— for code refactoringtest— for adding missing testschore— for routine tasks
-
When determining the commit message prefix, pick the most relevant option from the list above.
-
Use lowercase for all commit messages.
-
Use English for all commit messages.
-
If the change is not self-explanatory, include a bullet list of changes after a blank line below the summary.
-
Commit but not push. You can only push after my approval.
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 · 31 lines · 3 tokens per session scan A d588ad5a35eb
git_commit is a cursor rule published in the GitHub repository benyue1978/solo-flow-mcp (1 stars, last pushed 1y ago), licensed MIT. It adds 3 tokens to every session and 213 once invoked, about $0.0000 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
git
Git workflow — commit format, push policy, and PR process.
commit-sponsors
Every git commit message must acknowledge BetterDesk supporters.
no-ai-contributors
Never add AI tools as git authors or project contributors.
git-discipline
Commit, push, and branching rules. Owns ALL git behavior; other files state only their deviations.
git-commit-standards
Enforce structured Git commit messages.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.