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/olibartfast/neuriplo-infer/gitflow-workflowgit clone --depth 1 https://github.com/olibartfast/neuriplo-inferWrote 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/olibartfast/neuriplo-infer/gitflow-workflow)<a href="https://agentmods.dev/rules/olibartfast/neuriplo-infer/gitflow-workflow"><img src="https://agentmods.dev/badge/rules/olibartfast/neuriplo-infer/gitflow-workflow.svg" alt="Measured on agentmods" 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 | $0.01062 | $0.01062 |
| Opus 5 | $0.00531 | $0.00531 |
| Sonnet 5 | $0.00212 | $0.00212 |
| Haiku 4.5 | $0.00106 | $0.00106 |
Grade A, and why
gitflow-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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitFlow workflow (mandatory)
Follow the Atlassian GitFlow workflow.
In this repo, GitFlow main is master. develop is the integration branch.
Scope
GitFlow is mandatory for this coding repository. neuriplo-platform is the
architecture orchestrator (control plane) where GitFlow does not apply — work
there lands on main. See neuriplo-platform/ops/policies.yaml.
Branch roles
| GitFlow branch | This repo | Purpose |
|---|---|---|
main |
master |
Official release history; tag every release here |
develop |
develop |
Integration branch for completed features |
feature/* / feat/* |
feature/* / feat/* |
New work; parent is always develop |
release/* |
release/* |
Release prep (version, changelog, pins); no new features |
hotfix/* |
hotfix/* |
Production patches; parent is always master |
Never commit feature work directly to develop or master. Never merge features
into master. Never fork feature branches from master.
Agent Commit Signing
Every commit by an AI agent MUST include a Co-authored-by trailer with the
agent name, LLM model, and vendor email. See AGENTS.md "Agent Commit Signing"
for the full table of agents and format.
Feature workflow
git checkout develop && git pull
git checkout -b feat/<short-name> # or feature/<short-name>
# work, commit, push
# open PR: feat/<short-name> → develop
# after merge, delete the feature branch
Release workflow
When develop is ready to ship:
git checkout develop && git pull
git checkout -b release/<version> # e.g. release/0.5.0
# bump VERSION, CHANGELOG.md; run scripts/cut_release.sh <version>
# only release fixes/docs on this branch — no new features
git commit -m 'release: v<version>'
# PR or merge: release/<version> → master; tag v<version> on master
git checkout develop && git merge release/<version>
git branch -d release/<version>
git push origin --delete release/<version>
git push origin master develop --tags
# GitHub Release published by publish-github-release.yml after Release Guard
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.
- 4d ago First seen · 106 lines · 1,062 tokens per session scan A 85d013f18607
gitflow-workflow is a cursor rule published in the GitHub repository olibartfast/neuriplo-infer (103 stars, last pushed 3d ago), licensed MIT. It adds 1,062 tokens to every session, about $0.0053 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.