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/sordi-ai/skill-everythingWrote 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/sordi-ai/skill-everything/github-cli)<a href="https://agentmods.dev/rules/sordi-ai/skill-everything/github-cli"><img src="https://agentmods.dev/badge/rules/sordi-ai/skill-everything/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/sordi-ai/skill-everything/github-cli"><img src="https://agentmods.dev/badge/rules/sordi-ai/skill-everything/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.00022 | $0.00759 |
| Opus 5.5 | $0.00009 | $0.00304 |
| Sonnet 5.5 | $0.00004 | $0.00152 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
github-cli scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
12. **Use `gh api` for endpoints not covered by subcommands.** Prefer `gh api repos/{owner}/{repo}/pulls --jq '.[].number'` over raw `curl` with manual auth headers; `gh api` inherits the active auth context automaticall How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sub-Skill: GitHub CLI (gh) Conventions
Purpose: Consistent, auditable use of the gh CLI for PRs, issues, releases, and CI — preventing gate bypasses and silent failures.
Rules
Authentication & Scopes
- Check auth scope before scripting. Before running
ghin CI or scripts, always verify the required scopes are granted withgh auth status; missing scopes produce silent 404s rather than auth errors. - Use token env var in CI. Always pass
GH_TOKEN(orGITHUB_TOKEN) via environment variable in CI pipelines; never hard-code tokens or usegh auth login --with-tokeninteractively in automated contexts.
Pull Requests
- Include all required labels on PR creation. Always pass
--labelfor every gate-required label when runninggh pr create; omitting a label silently bypasses automated approval gates. Reference: ERR-2026-023 - Set reviewer on creation. Always use
--reviewer <handle>when creating PRs that require CODEOWNERS approval; adding reviewers after creation delays the review clock. - Open as draft when work is incomplete. Use
gh pr create --draftfor PRs not yet ready for review; never open a ready-for-review PR on a branch with failing CI. - Link issues explicitly. Always include
--body "Closes #<issue>"or--body "Fixes #<issue>"so GitHub auto-closes the linked issue on merge; never rely on branch name alone for issue linkage.
Issues
- Assign and label on creation. Use
gh issue create --assignee @me --label <label>rather than creating bare issues and editing them in a second step; unassigned, unlabelled issues fall out of triage queues. - Use JSON output for scripting. Prefer
gh issue list --json number,title,labelsover parsing human-readable output; the--jsonflag is stable acrossghversions, plain text is not.
CI / Workflows
- Trigger runs explicitly when needed. Use
gh workflow run <workflow.yml> --ref <branch>to trigger a workflow rather than pushing an empty commit; empty commits pollute history. - Watch run status in scripts. After triggering a workflow, use
gh run watch <run-id>or pollgh run view <run-id> --json conclusionrather than sleeping for a fixed duration.
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 · 48 lines · 22 tokens per session scan A f397c934b6e9
github-cli is a cursor rule published in the GitHub repository sordi-ai/skill-everything (20 stars, last pushed 5mo ago), licensed MIT. It adds 22 tokens to every session and 759 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
github
GitHub repository operations: PRs, issues, releases, branch protection, CODEOWNERS, Dependabot, and repo settings audits. Use when user says 'review my PR', 'create a release', 'cut a release', 'tag a release', 'set up branch protection', 'add CODEOWNERS', 'audit repo settings', 'is Dependabot configured', or asks…
release-notes
Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.
release-ops-demo
Agent rules for release-ops-demo.
release
Git tag, CHANGELOG heading, package.json, and npm publish must share one semver. Use when releasing, shipping, deploying, tagging, or publishing npm.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.