What is testing-gh-skills?

A manually triggered test tool for GitHub command-line search skills. It runs a Python test coordinator across six skill groups and produces test reports and review notes.

Running the full GitHub search-skill test suite, validating responses, and reviewing the generated results.

It checks many search cases in fresh sessions and keeps test instructions separate from the requests being tested.

testing-gh-skills — Skill for Claude Code by aaddrick: A manually triggered test tool for GitHub command-line search…

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add aaddrick/gh-cli-search

Claude Code

/plugin install gh-cli-search

Made for: Claude Code.

Or install gh-cli-search, the plugin that ships this one along with the rest of its 9 skills, 1 command, 3 agents, 1 hook.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/aaddrick/gh-cli-search/testing-gh-skills.svg)](https://agentmods.dev/skills/aaddrick/gh-cli-search/testing-gh-skills)

Your own site

<a href="https://agentmods.dev/skills/aaddrick/gh-cli-search/testing-gh-skills"><img src="https://agentmods.dev/badge/skills/aaddrick/gh-cli-search/testing-gh-skills.svg" alt="Measured on agentmods" height="20"></a>

Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,817 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00040	$0.02817
Opus 5	$0.00020	$0.01409
Sonnet 5	$0.00008	$0.00563
Haiku 4.5	$0.00004	$0.00282

Measured 6d ago against content hash 93489a4249c8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

testing-gh-skills 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 6d 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.

skills/testing-gh-skills/SKILL.md · 337 lines

How it starts

The opening of the file, as written. The whole thing — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Testing GitHub CLI Search Skills

⚠️ CRITICAL: Slash Command Only

This skill should NEVER be invoked automatically.

ONLY invoke this skill when:

User explicitly runs /test-gh-skills slash command
User explicitly requests "run the test suite"

DO NOT invoke when:

User asks about testing in general
User asks how to test
User mentions the word "test" in any context
You think testing would be helpful
ANY other scenario

Why: Running the full test suite takes ~8 minutes and 80 Claude API calls. This is expensive and should only happen on explicit user request via the slash command.

Overview

Execute comprehensive test suite for all gh CLI search skills using a Python test orchestrator. The script runs 80 tests in parallel (default: 4 workers), validates responses, and generates detailed reports at multiple levels. After test execution completes, the test-reviewer agent automatically analyzes results and creates REVIEWER-NOTES.md.

Core Principle: Fast, efficient test execution with minimal overhead. Each test runs in a fresh Claude session with only the user request (no test criteria leaked).

Performance: ~6 seconds per test, ~2-3 minutes total for 80 tests with parallel execution (4 workers).

When to Use

ONLY use this skill when user explicitly invokes:

/test-gh-skills slash command
Direct request: "run the full test suite"
Direct request: "execute all tests"

NEVER use automatically for:

Testing a single command manually (use ./testing/scripts/run-single-test.sh directly)
Skills haven't been created yet
Need to write new test scenarios first
User asks about testing concepts
User mentions testing in passing

Architecture

python3 testing/scripts/run-all-tests.py [--workers N] [--no-review]
  ├─> Parse all scenario files in testing/scenarios/
  ├─> For each test group (6 groups total):
  │   ├─> Submit tests to parallel worker pool (default: 4 workers)
  │   ├─> Each worker executes: ./testing/scripts/run-single-test.sh "<user-request>"
  │   │   └─> claude -p "<user-request>" --allowedTools "Read,Skill"
  │   ├─> Extract command from response
  │   ├─> Validate against expected criteria
  │   └─> Write test report
  ├─> Generate group reports (per scenario file)
  ├─> Generate master report (all tests)
  └─> Automatically invoke test-reviewer agent (headless)
      ├─> Read master report
      ├─> Analyze group reports
      ├─> Sample individual test failures (3-5 examples)
      ├─> Identify failure patterns
      ├─> Perform root cause analysis
      └─> Create REVIEWER-NOTES.md with recommendations

Total: 80 tests across 6 groups (parallel execution with 4 workers) + automatic review

Read the full file on GitHub · 337 lines

Changes

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.

6d ago First seen · 337 lines · 40 tokens per session scan A 93489a4249c8

Subscribe to this mod's changes

testing-gh-skills is a skill published in the GitHub repository aaddrick/gh-cli-search (8 stars, last pushed 9mo ago), licensed MIT. It adds 40 tokens to every session and 2,817 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.

Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

testing-gh-skills