Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Sartori-RIA/ubuteco_apinpx agentmods add rules/sartori-ria/ubuteco_api/plan-and-git-workflowWrote 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/sartori-ria/ubuteco_api/plan-and-git-workflow)<a href="https://agentmods.dev/rules/sartori-ria/ubuteco_api/plan-and-git-workflow"><img src="https://agentmods.dev/badge/rules/sartori-ria/ubuteco_api/plan-and-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/sartori-ria/ubuteco_api/plan-and-git-workflow"><img src="https://agentmods.dev/badge/rules/sartori-ria/ubuteco_api/plan-and-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.00509 | $0.00509 |
| Opus 5.5 | $0.00204 | $0.00204 |
| Sonnet 5.5 | $0.00102 | $0.00102 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
plan-and-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 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
Plan & git workflow (ubuteco_api)
Mirror of
docs/workflow-plans-and-git.md— edit the doc first, then sync this file.
Applies when implementing docs/plans/ in ubuteco_api.
Before opening a PR (mandatory)
Plan & docs
- Open the plan doc (
docs/plans/NN-*.md) anddocs/plans/README.md. - Mark completed phases with
[x], set headerStatus: completed(orin progressif deliberately partial). - Include plan doc updates in the same feature branch / PR as the code.
- PR title/body must name the plan and link
docs/plans/....
Plan-only edits with no code may go direct to master per AGENTS.md.
Quality gates (must pass before push / PR)
| Check | Command |
|---|---|
| RuboCop | bin/rubocop |
| RSpec | bundle exec rspec |
| Code coverage | With RSpec (SimpleCov → coverage/) |
| Brakeman | bin/brakeman --quiet --no-pager --exit-on-warn --exit-on-error |
| bundler-audit | bin/bundler-audit check --update |
| OpenAPI drift (if contract changed) | bundle exec rake openapi:drift_check |
| Plan status drift (if plan docs changed) | bin/plans_drift_check |
Shortcut: bin/ci. Do not open a PR with failures.
Commits: small and focused
One logical change per commit (docs, feat, test, fix, refactor). One plan → one branch → one PR: feature/<plan-slug>.
PR checklist
- Plan doc + README status updated
- RuboCop, RSpec + coverage, Brakeman, bundler-audit green
- Small commit history
- Test plan in PR body
- Companion React PR linked if cross-stack
Full reference: docs/workflow-plans-and-git.md.
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 · 50 lines · 509 tokens per session scan A 9aabb2cdfc72
plan-and-git-workflow is a cursor rule published in the GitHub repository Sartori-RIA/ubuteco_api (10 stars, last pushed 4mo ago), licensed MIT. It adds 509 tokens to every session, about $0.0020 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.
commits
Conventional Commits standards for clear, semantic commit messages.
no-ai-contributors
Never add AI tools as git authors or project contributors.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.
git-discipline
Commit, push, and branching rules. Owns ALL git behavior; other files state only their deviations.