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/openjkai/secscan_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/openjkai/secscan_mcp/git-workflow)<a href="https://agentmods.dev/rules/openjkai/secscan_mcp/git-workflow"><img src="https://agentmods.dev/badge/rules/openjkai/secscan_mcp/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/openjkai/secscan_mcp/git-workflow"><img src="https://agentmods.dev/badge/rules/openjkai/secscan_mcp/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.00202 | $0.00202 |
| Opus 5.5 | $0.00081 | $0.00081 |
| Sonnet 5.5 | $0.00040 | $0.00040 |
| Haiku 4.5 | $0.00020 | $0.00020 |
Grade A, and why
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 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 workflow
- Default branch:
main - Prefer feature branches off
main:feat/gitleaks-adapter,fix/path-validation(avoid committing large changes directly onmainwhen collaborating) - Keep PRs small and aligned with PLAN.md todos
- Run
make checkbefore opening a PR - PRs: use
gh pr createwhen user asks; include Summary + Test plan
What not to commit
- Virtualenv (
.venv/) - Tool caches (
.ruff_cache,.mypy_cache,.pytest_cache) - Generated scan reports with real project data unless sanitized fixtures in
tests/fixtures/
Hooks
Pre-commit enforces: trailing whitespace, YAML/TOML/JSON checks, private key detection, ruff, ruff-format, mypy on src/.
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 · 23 lines · 202 tokens per session scan A 12ff57f83f4f
git-workflow is a cursor rule published in the GitHub repository openjkai/secscan_mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 202 tokens to every session, about $0.0008 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
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.