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/cdbattags/aiWrote 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/cdbattags/ai/github-repo-triage)<a href="https://agentmods.dev/rules/cdbattags/ai/github-repo-triage"><img src="https://agentmods.dev/badge/rules/cdbattags/ai/github-repo-triage/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/cdbattags/ai/github-repo-triage"><img src="https://agentmods.dev/badge/rules/cdbattags/ai/github-repo-triage.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.00459 | $0.00459 |
| Opus 5.5 | $0.00184 | $0.00184 |
| Sonnet 5.5 | $0.00092 | $0.00092 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
github-repo-triage 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
GitHub Repo Triage & Maintenance
Tone & Voice
Christian is direct. Bullet points over prose. Show the assessment, propose the action, wait for approval. Don't over-explain — he'll ask if he needs more.
- Present triage results as ranked tables (tier/priority, not paragraphs)
- Propose commit messages inline, wait for "yes" before committing
- When closing issues/PRs, leave helpful public comments (thank contributors, link commits)
- Use conventional commit prefixes:
feat:,fix:,chore:,docs:
Git Keywords That Auto-Close
These keywords in commit messages auto-close issues/PRs when pushed to the default branch:
Closes #N,Fixes #N,Resolves #N(case-insensitive)- Multiple:
Closes #36 Closes #40(space-separated, same line) - Works for issues AND PRs if the commit lands on the default branch
If a PR was cherry-picked (not merged via GitHub), it auto-closes from the Closes keyword but won't show as "merged" — it shows as "closed". Add a comment linking the commit SHA so contributors see their work was included.
Co-Authored-By Attribution
When cherry-picking from PRs, always add Co-authored-by trailers:
Co-authored-by: Full Name <[email protected]>
Get the real email — don't guess:
# Check the PR's actual commit author
gh api repos/{owner}/{repo}/pulls/<N>/commits --jq '.[].commit.author | "\(.name) <\(.email)>"'
If the commit name is an internal username (e.g., xlw116), use the GitHub display name instead but keep the commit email.
For Detailed Workflow
Read the github-repo-triage skill for the full triage, cherry-pick, release, and publishing workflow.
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 · 47 lines · 459 tokens per session scan A 0c54e1d91f3c
github-repo-triage is a cursor rule published in the GitHub repository cdbattags/ai (5 stars, last pushed 7mo ago), licensed MIT. It adds 459 tokens to every session, about $0.0018 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
git-workflow
Git workflow: commits, branches, PRs, history management.
git-master
Git operations — clean commits, PR prep, conflict resolution, change summaries.
publishing-dotnettool
This file serves as a guideline for the Cursor AI Agent to ensure the proper creation, packaging, and publishing of a dotnet tool. Follow these rules to maintain consistency, quality, and security across published tools.
12-new-project
Workflow for starting a new app from this template - rebranding, identity, cleanup and first feature.
13-updating-project
Workflow for updating an existing project - dependency and SDK upgrades, migrations, refactors, bug fixes.
development-workflow-rule
Comprehensive development workflow system for task tracking, testing, and version control.