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/metagit-ai/metagit-cliWrote 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/metagit-ai/metagit-cli/github-cli)<a href="https://agentmods.dev/rules/metagit-ai/metagit-cli/github-cli"><img src="https://agentmods.dev/badge/rules/metagit-ai/metagit-cli/github-cli/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/metagit-ai/metagit-cli/github-cli"><img src="https://agentmods.dev/badge/rules/metagit-ai/metagit-cli/github-cli.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.00240 | $0.00240 |
| Opus 5.5 | $0.00096 | $0.00096 |
| Sonnet 5.5 | $0.00048 | $0.00048 |
| Haiku 4.5 | $0.00024 | $0.00024 |
Grade A, and why
github-cli 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 CLI authentication
Before any gh command (gh pr create, gh issue, gh run, etc.), unset stale token environment variables that override the keyring login:
env -u GH_TOKEN -u GITHUB_TOKEN gh <subcommand> ...
Why
An invalid or expired GH_TOKEN / GITHUB_TOKEN in the shell environment causes HTTP 401: Bad credentials even when gh auth status shows a valid keyring account (with "Active account: false" on the keyring entry).
Checklist for PRs
- Push branch:
git push -u origin HEAD(SSH/git creds are separate fromgh). - Create PR:
env -u GH_TOKEN -u GITHUB_TOKEN gh pr create ... - If auth still fails:
gh auth statusthengh auth loginif needed.
Do not export GH_TOKEN for local gh unless intentionally using that token for the session.
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 · 25 lines · 240 tokens per session scan A d249be7094e7
github-cli is a cursor rule published in the GitHub repository metagit-ai/metagit-cli (3 stars, last pushed 14d ago), licensed MIT. It adds 240 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
new-project-standard
Local adoption files are authoritative. Remote links are navigation only and must not be fetched or executed at runtime.
git-workflow
Branch hygiene — rebase on main before every PR and keep branches synced.
release-checklist
What to update with each code change or version release.
check
Analyze staged git changes with archguardian before committing.
git-workflow
Git workflow: commits, branches, PRs, history management.
self_improve
description: Guidelines for continuously improving Cursor rules based on emerging code patterns and best practices. globs: / alwaysApply: true.