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/mamahoos/dot-filesWrote 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/mamahoos/dot-files/github-workflow)<a href="https://agentmods.dev/rules/mamahoos/dot-files/github-workflow"><img src="https://agentmods.dev/badge/rules/mamahoos/dot-files/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/mamahoos/dot-files/github-workflow"><img src="https://agentmods.dev/badge/rules/mamahoos/dot-files/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.00615 | $0.00615 |
| Opus 5.5 | $0.00246 | $0.00246 |
| Sonnet 5.5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Workflow
Commits and branches: git-workflow-and-versioning. Issues, PRs, labels, assignees, reviews, merge: this rule. Before creating or editing an issue or PR, load .cursor/skills/github-workflow/SKILL.md — do not improvise gh flags.
Linked bodies — tick before merge
Scope is the PR body plus every issue it names with Closes / Fixes / Resolves #N, open or closed. - [ ] and * [ ] are unfinished work: do the work, PATCH the body to - [x], and never tick what you did not verify. After gh pr merge is too late.
Run this on the PR number and every linked issue number; if it prints anything, do not merge:
if gh api "repos/OWNER/REPO/issues/N" --jq .body | command grep -E '^[[:space:]]*[-*][[:space:]]+\[ \]'; then
exit 1
fi
Standard flow (mandatory on these use cases)
issue → branch → PR with Closes #N → label + assignee → tick boxes → grep gate → review → green checks → merge
Required when: the user asked for GitHub flow, an issue, or a PR; a bug has a durable repro; a feature needs acceptance criteria; work spans multiple PRs; other humans will review, or it is breaking / security / public behavior; it touches CI, install, or shared automation; an issue already covers it (Closes #N). Do not skip the flow to "avoid spam".
Do not open an issue for a one-file chore, a typo, or "so the PR has a number". Never invent Closes.
Discover, don't invent
Read the repo before acting: gh repo view --json nameWithOwner,defaultBranchRef, gh label list, and the collaborator list. Never create labels. Never assign or request review from a login that is not a collaborator, and never from the PR author.
Exactly one type label if it exists: bug | enhancement | chore | documentation; ask if it is missing. automated only on bot/sync PRs.
Assign, review, merge
--assignee "@me"when the authenticated user is a collaborator; ask when other humans have push.- Ask before a GitHub review when the diff is large or touches more than a few files.
- Solo:
gh pr review --comment, never--approveon your own PR. - Merge only when
gh pr checksis green and the grep gate above prints nothing.
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 · 42 lines · 615 tokens per session scan A b73315d18cab
github-workflow is a cursor rule published in the GitHub repository mamahoos/dot-files (5 stars, last pushed yesterday), licensed MIT. It adds 615 tokens to every session, about $0.0025 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-09-04.
Other cursor rules, from other repositories
git
Git rules. Conventional commits, atomic staging, no force push.
release-ts-sdk
Release @aptos-labs/ts-sdk or @aptos-labs/confidential-asset — version bump, changelog stamp, release PR, then tag + GitHub Release that triggers NPM publish.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.
40-git-safety
Git safety rule for branches, commits, pushes, and destructive Git commands.
git-master
Git operations — clean commits, PR prep, conflict resolution, change summaries.
git-workflow
Git branching and PR workflow.