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.
npx agentmods add skills/anilcancakir/claude-code-plugin/github-clinpx skills add anilcancakir/claude-code-plugin --skill github-cligit clone --depth 1 https://github.com/anilcancakir/claude-code-pluginWhat 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.00039 | $0.02812 |
| Opus 5 | $0.00019 | $0.01406 |
| Sonnet 5 | $0.00008 | $0.00562 |
| Haiku 4.5 | $0.00004 | $0.00281 |
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 2d 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.
Use `gh` (GitHub CLI) for all GitHub operations. Prefer `gh` over raw API calls, `curl`, or web browser. Every `gh` command supports `--help` for flag discovery. How it starts
The opening of the file, as written. The whole thing — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub CLI Skill
Use gh (GitHub CLI) for all GitHub operations. Prefer gh over raw API calls, curl, or web browser. Every gh command supports --help for flag discovery.
Principles
- JSON first: Add
--json <fields>+--jq <query>for machine-readable output in scripts - Repo context: Run commands from a git repo directory —
ghauto-detects{owner}and{repo} - Cross-repo: Use
-R owner/repoflag to target a different repository - No interactive prompts: Always pass
--title,--body, flags explicitly — never rely on interactive prompts - Rate limits: Add
sleep 1between iterations in bulk loops
Issues
Create
gh issue create --title "Bug: login fails" --body "Steps to reproduce..." --label bug --assignee @me
gh issue create --title "Feature request" --body-file description.md --label enhancement --project "Roadmap"
List & Filter
gh issue list # Open issues (default 30)
gh issue list --state all --limit 100 # All states, more results
gh issue list --label "bug" --assignee @me # By label + assignee
gh issue list --search "error no:assignee sort:created-asc" # Advanced search query
gh issue list --json number,title,labels --jq '.[].title' # JSON + jq
View & Modify
gh issue view 123 # View issue details
gh issue view 123 --json body,comments --jq '.comments[-1].body' # Last comment
gh issue comment 123 --body "Working on this"
gh issue edit 123 --add-label "in-progress" --remove-label "needs-triage"
gh issue close 123 --reason completed
gh issue reopen 123
Link to PR
Reference issues in PR body with Fixes #123 or Closes #123 — GitHub auto-closes on merge.
Pull Requests
Create
gh pr create --title "feat: add auth" --body "Implements OAuth2 flow" --base main
gh pr create --fill # Auto-fill from commit messages
gh pr create --fill-verbose # Commits msg+body in description
gh pr create --draft # Draft PR
gh pr create --reviewer user1,team-name --label feature --assignee @me
gh pr create --body-file pr-description.md
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.
- 2d ago First seen · 339 lines · 39 tokens per session scan A 8f8ca4808b6a
github-cli is a skill published in the GitHub repository anilcancakir/claude-code-plugin (2 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 2,812 once invoked, about $0.0002 per session on Opus 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-31.
Other skills, from other repositories
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
python-package-management
Guide for managing packages in the Agent Framework Python monorepo, including creating new connector packages, versioning, and the lazy-loading pattern. Use this when adding, modifying, or releasing packages.
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
python-code-quality
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.