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/agents-squads/squads-cli/ghnpx skills add agents-squads/squads-cli --skill ghgit clone --depth 1 https://github.com/agents-squads/squads-cliWhat 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.00000 | $0.00402 |
| Opus 5 | $0.00000 | $0.00201 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
gh 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 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.
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
gh — GitHub CLI Operations
You have access to gh (GitHub CLI) for repository and project management.
Issues
gh issue list # List open issues
gh issue list --label "bug" # Filter by label
gh issue view <number> # View issue details
gh issue create --title "..." --body "..." # Create issue
gh issue close <number> # Close issue
gh issue comment <number> --body "..." # Add comment
Pull Requests
gh pr list # List open PRs
gh pr view <number> # View PR details
gh pr create --title "..." --body "..." # Create PR
gh pr merge <number> # Merge PR
gh pr review <number> --approve # Approve PR
gh pr checks <number> # View CI status
gh pr diff <number> # View PR diff
Repository
gh repo view # View repo info
gh repo clone <owner/repo> # Clone repo
gh api repos/<owner>/<repo> # Raw API access
Workflow Runs
gh run list # List recent runs
gh run view <id> # View run details
gh run watch <id> # Watch run in progress
Search
gh search repos "<query>" # Search repos
gh search issues "<query>" # Search issues
gh search prs "<query>" # Search PRs
Best Practices
- Check before creating: Search existing issues/PRs before creating duplicates
- Use labels: Filter and organize with labels
- Link issues: Reference issues in PR descriptions with
Fixes #N - Review CI: Always check
gh pr checksbefore merging
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 · 58 lines · 0 tokens per session scan A 0771b53bb38e
gh is a skill published in the GitHub repository agents-squads/squads-cli (51 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 402 tokens. 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-30.
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.
verify-samples-tool
How to use the verify-samples tool to run, verify, and manage sample definitions in the Agent Framework repository. Use this when adding, updating, or running sample verification.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
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.