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/mikeysrecipes/mcp-openvisionWrote 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/mikeysrecipes/mcp-openvision/gitpush)<a href="https://agentmods.dev/rules/mikeysrecipes/mcp-openvision/gitpush"><img src="https://agentmods.dev/badge/rules/mikeysrecipes/mcp-openvision/gitpush/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/mikeysrecipes/mcp-openvision/gitpush"><img src="https://agentmods.dev/badge/rules/mikeysrecipes/mcp-openvision/gitpush.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.00000 | $0.00247 |
| Opus 5.5 | $0.00000 | $0.00099 |
| Sonnet 5.5 | $0.00000 | $0.00049 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
gitpush 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.
This is a copy
100% identical to gitpush — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Git Push Manual Rule
Context
Used when user indicates they want to update all saved changes in git
Critical Rules
- Run the command
git add .from the root of the workspace - Review all added changes that will be included in the commit
- Use format for title:
type: brief description- keep it brief and descriptive (max 72 chars) - Add two line breaks after commit title
- Include short paragraph summary of gist of what and why the change is being made and end with " -Agent Generated Commit Message"
- Push all to the remote current branch
Examples
Updated the readme to include a better diagram showing rules workflow, while
also adding more sample rules to show rule folder organization. Specifically, notice that the change to .cursor/rules/*folders include readme.md files also to aid in understanding the folders purpose for human developers. AI gets its understanding from .cursor/rules/rule-generating-agent.mdc instead.
-Agent Generated Commit Message
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 · 36 lines · 0 tokens per session scan A 9c6edf4760da
gitpush is a cursor rule published in the GitHub repository mikeysrecipes/mcp-openvision (1 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 247 tokens. A static security scan graded it A with 0 findings. It is 100% identical to gitpush, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
rebase-only-merged-agents
When rebasing after a merge, only rebase the agents whose branches you just merged. Do not rebase agents that are still running.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
git-workflow
Rules for git operations, commit strategy, and GitHub CLI usage.
release-checklist
What to update with each code change or version release.
git-workflow
Git commit format and PR process - conventional commits.
branching-merging-strategy
This is a set of instructions to the AI Assistant for branching and merging strategy.