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 skills add ychampion/cskill-agents --skill skip-skill-listing-in-test-environmentgit clone --depth 1 https://github.com/ychampion/cskill-agentsWrote 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/skills/ychampion/cskill-agents/skip-skill-listing-in-test-environment)<a href="https://agentmods.dev/skills/ychampion/cskill-agents/skip-skill-listing-in-test-environment"><img src="https://agentmods.dev/badge/skills/ychampion/cskill-agents/skip-skill-listing-in-test-environment/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/skills/ychampion/cskill-agents/skip-skill-listing-in-test-environment"><img src="https://agentmods.dev/badge/skills/ychampion/cskill-agents/skip-skill-listing-in-test-environment.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.00030 | $0.00406 |
| Opus 5.5 | $0.00012 | $0.00162 |
| Sonnet 5.5 | $0.00006 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
skip-skill-listing-in-test-environment 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 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.
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
SKILL: Skip Skill Listing in Test Environment
Domain: command-surfaces
Trigger: Apply when tests exercise attachment-building code paths but do not need discoverability payloads such as skill listings.
Source Pattern: Distilled from reviewed command-surface and listing-control patterns.
Core Method
Treat test runs as a separate operating mode where non-essential discoverability output should be silent by default. Check the environment before computing any listing state, and return an empty result immediately when the process is running under tests. This keeps tests focused on actionable behavior, avoids large incidental payloads in assertions and fixtures, and prevents test outcomes from drifting because of unrelated skill-registry changes.
Key Rules
- Put the test-environment guard at the top of the attachment builder so no listing work or state mutation happens before the early exit.
- Suppress only non-essential discoverability payloads; do not use the pattern to hide behavior that tests are explicitly meant to verify.
- Prefer deterministic environment checks such as
NODE_ENV === 'test'over indirect heuristics. - Keep tests isolated from runtime inventory churn so new skills or registry changes do not force unrelated snapshot or transcript updates.
Example Application
If a chat runtime test exercises the attachment pipeline to validate message ordering, skip the skill-listing attachment entirely when NODE_ENV is test. The test still covers the real behavior under examination without needing to account for a changing skill registry or extra discoverability tokens.
Anti-Patterns (What NOT to do)
- Do not generate large listing attachments in tests when those attachments are irrelevant to the assertion; they add noise and make fixtures brittle.
- Do not place the test guard after registry lookups or sent-state mutation; the point is to avoid both the output and the work.
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 · 28 lines · 30 tokens per session scan A 3bb00c9a49fb
skip-skill-listing-in-test-environment is a skill published in the GitHub repository ychampion/cskill-agents (36 stars, last pushed 6mo ago), licensed MIT. It adds 30 tokens to every session and 406 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
verify
Prove a completion claim with fresh evidence before making it — the gate's exit code, the real diff, the remote's checks, the reviewer's verdict.
rudder
Use locally captured coding-session intent to resolve a device-local behavioral spec, generate focused tests from that spec, implement the smallest production changes through red-green TDD, and verify coverage with the repository's native tooling. Use when the user asks to run Rudder, create or regenerate tests for…
qamap-pr-qa
PR bug review and test planning with QAMap. Run qamap qa brief once; it prints the diff, each changed declaration's tests and callers with assertion lines, QA focus and unknowns in one bounded local response, so the review starts from it instead of re-exploring the repository.
ux-review
Verify a shipped UI against objective design gates — WCAG accessibility, design-token fidelity, responsive/render integrity, interaction & state coverage, and visual regression — by rendering it in a real browser. Use for 'ux review', 'a11y check', 'does this UI hold up', or /ux-review. Enforces design quality; does…
adding-an-audit-check
Add a new audit check to agent-context-doctor end to end, including config, suppressions, the check catalog, tests, and docs. Use when asked to detect a new kind of problem in agent instruction files.
verify
Run x-harness read-only verification.