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/aaddrick/gh-cli-search/using-gh-cli-searchnpx skills add aaddrick/gh-cli-search --skill using-gh-cli-searchgit clone --depth 1 https://github.com/aaddrick/gh-cli-searchWhat 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.00037 | $0.01101 |
| Opus 5 | $0.00018 | $0.00550 |
| Sonnet 5 | $0.00007 | $0.00220 |
| Haiku 4.5 | $0.00004 | $0.00110 |
Grade A, and why
using-gh-cli-search 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.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This is not a suggestion. This is not optional. You cannot rationalize your way out of this.
Why: GitHub CLI search syntax is full of pitfalls. The -- flag. Quoting rules. PowerShell escaping. Platform differences. You WILL get it wrong without the skills. The user will copy-paste your broken command. They will waste time debugging YOUR mistake.
GitHub CLI Search Protocol
MANDATORY DETECTION PROTOCOL
When a user message mentions ANY of these, you MUST use gh-cli-search skills:
- ☐ Searching on GitHub
- ☐ Finding code/issues/PRs/commits/repos
- ☐
gh searchcommand - ☐ GitHub CLI queries
- ☐ Installing/troubleshooting gh CLI
If detected → Use the Skill tool to load the appropriate gh-cli-search skill
Available Skills
You have access to these gh-cli-search skills:
- gh-search-code - Searching for code across repositories
- gh-search-commits - Searching commit history
- gh-search-issues - Searching issues (and PRs)
- gh-search-prs - Searching pull requests specifically
- gh-search-repos - Searching for repositories
- gh-cli-setup - Installation and troubleshooting
Pick the right skill. Use the Skill tool. Follow it exactly.
Common Rationalizations That Mean You're About To Fail
If you catch yourself thinking ANY of these thoughts, STOP. You are about to give the user a broken command.
- "This is just a simple search query" → WRONG. Simple queries still need correct quoting and the
--flag for exclusions. - "I know gh CLI syntax" → WRONG. You know SOME of it. The skills know ALL of it, including edge cases.
- "I'll just construct the command myself" → WRONG. You will forget the
--flag. Or quote incorrectly. Or miss PowerShell escaping. - "The user didn't explicitly say 'gh search'" → WRONG. If they're asking about GitHub searching via CLI, they need these skills.
- "I can figure out the syntax quickly" → WRONG. The skills exist because this is NOT quick. You will make mistakes.
- "Let me try without the skill first" → WRONG. The skill IS the first step. Not the fallback.
- "This doesn't need the full skill treatment" → WRONG. Every GitHub CLI search command needs correct syntax. Use the skill.
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 · 117 lines · 37 tokens per session scan A 3f9b79e96432
using-gh-cli-search is a skill published in the GitHub repository aaddrick/gh-cli-search (8 stars, last pushed 9mo ago), licensed MIT. It adds 37 tokens to every session and 1,101 once invoked, about $0.0002 per session on Opus 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.