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/sotayamashita/openapi-mcp-serverWrote 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/sotayamashita/openapi-mcp-server/git-github-workflow)<a href="https://agentmods.dev/rules/sotayamashita/openapi-mcp-server/git-github-workflow"><img src="https://agentmods.dev/badge/rules/sotayamashita/openapi-mcp-server/git-github-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/sotayamashita/openapi-mcp-server/git-github-workflow"><img src="https://agentmods.dev/badge/rules/sotayamashita/openapi-mcp-server/git-github-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.00253 | $0.00253 |
| Opus 5.5 | $0.00101 | $0.00101 |
| Sonnet 5.5 | $0.00051 | $0.00051 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
git-github-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
When asked, to create a commit:
- Run
git statusto check changes - Run
git commitfollowing Conventional Commits format in English (<type>[optional scope]: <description>) - Help commit meaningful units of change rather than staging everything
- Use
git diff [optional file(s)] | catwhen diff is needed.
When asked, to submit a PR (Note: Use gh and assume I am already authenticated correctly):
- Run
git statusto check changes - Run
git add .to add all the changes to the staging area (IF NEEDED) - Run
git committo commit changes (IF NEEDED) - Run
git pushto push the changes to the remote repository (IF NEEDED) - Run
git branchto check the current branch - Run
git log main..[Insert current branch] - Run
git diff --name-status mainto check to see what files have been changed - Run
gh pr create --title "Title goes here..." --body "Example body..."
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 · 21 lines · 253 tokens per session scan A a6e8c016a006
git-github-workflow is a cursor rule published in the GitHub repository sotayamashita/openapi-mcp-server (7 stars, last pushed yesterday), licensed MIT. It adds 253 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
windsurfrules
Pare wraps CLI tools in MCP servers returning structured JSON. Always prefer Pare MCP tools over raw CLI.
conventional-commits
Enforce Conventional Commits format for all commit messages.
project-structure
The Swagger Navigator MCP is a Model Context Protocol server for intelligent discovery and search of Swagger/OpenAPI endpoints.
typescript-standards
// Good: Typed error handling function loadConfig(): Config { try { // ... loading logic } catch (error) { if (error instanceof yaml.YAMLException) { throw new Error(Invalid YAML in configuration file: ${error.message}); } throw error; } }.
testing-standards
Cursor rule "testing-standards" from aaydin-tr/swagger-navigator-mcp, covering testing standards, test structure, coverage requirements, test organization and mocking guidelines.
git-workflow
Vollagentische Entwicklung, Auto-Commits, Commit-Konventionen.