A set of rules for keeping a GitHub repository secure and orderly when changing GitHub configuration or community files. It covers CI, releases, branch and tag protections, security reporting, and pinned Actions.

Updating .github files, SECURITY.md, CONTRIBUTING.md, tags, workflows, and GitHub Releases. It defines how CI and release workflows should run and how security issues should be reported.

It prevents common mistakes such as confusing a releases folder with a GitHub Release, using unpinned automation, exposing secrets, or weakening protection on important branches and tags.

github — Cursor rule for coding agents by mhmdreza-rafiei: A set of rules for keeping a GitHub repository…

Install

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.

agentmods

npx agentmods add rules/mhmdreza-rafiei/agent-tools/github

Clone the repo

git clone --depth 1 https://github.com/mhmdreza-rafiei/agent-tools

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/github.svg)](https://agentmods.dev/rules/mhmdreza-rafiei/agent-tools/github)

Your own site

<a href="https://agentmods.dev/rules/mhmdreza-rafiei/agent-tools/github"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/github.svg" alt="Measured on agentmods" height="20"></a>

Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 314 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00029	$0.00314
Opus 5	$0.00015	$0.00157
Sonnet 5	$0.00006	$0.00063
Haiku 4.5	$0.00003	$0.00031

Measured 3d ago against content hash 3cb436548f9c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

github 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 3d 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.

rules/github.mdc · 30 lines

What it actually says

GitHub

Applies when the change touches .github/, SECURITY.md, CONTRIBUTING.md, tags, or GitHub Releases. Not every chat.

Must

GitHub Releases come from v* tags + a workflow. A folder named releases/ is only a built artifact in the tree.
Pin Actions by commit SHA, not a floating major tag.
CI on pull requests and on the default branch. Read-only contents unless the job publishes a Release (contents: write then).
SECURITY.md tells people to use private advisories, not public issues.
Tag ruleset: v* cannot be deleted, moved, or force-updated.
main cannot be deleted or force-pushed. Do not require approving reviews unless the user asked (solo push to main is how this catalog ships).

Do not

Do not treat the releases/ directory as a GitHub Release.
Do not enable "required reviews" on a one-person repo without asking.
Do not commit secrets, tokens, or .env.
Do not skip CI to land a catalog change (lint-artifacts, check-compat).

Changes

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.

3d ago First seen · 30 lines · 29 tokens per session scan A 3cb436548f9c

Subscribe to this mod's changes

github is a cursor rule published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 16d ago), licensed MIT. It adds 29 tokens to every session and 314 once invoked, about $0.0001 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-31.

Git and workflow Releases Security

08-github-workflow-standards

GitHub issue/PR/milestone standards for Matryca Plumber (OSS maintainer rigor).

MarcoPorcellato/matryca-plumber · 21 tokens

versioning

Semantic versioning rules for tagging releases.

git-treeline/cli · 324 tokens

versioning-and-npm-distribution

Versioning integrity and GitHub/npm distribution flow for AgentProdReady.

ameenmari/agentprodready · 449 tokens

release-checklist

What to update with each code change or version release.

yoreai/relay · 215 tokens

release

Cut a versioned release of harness-mini — bump VERSION, roll the CHANGELOG, tag, and publish a GitHub release. Use when shipping a new version. Wraps bin/harness.sh release; covers the human-judgment steps (semver choice, changelog curation) the script can't make.

harness-mini/harness-mini · 64 tokens

130-version-management

Update the version of the MCP server.

blockscout/mcp-server · 7 tokens