test

test is a skill for Claude Code from usk6666/yorishiro-proxy. It costs 3 tokens per session (209 once invoked), scanned A, original, Apache-2.0.

A workflow for running Go tests, which check that Go program code behaves as expected.

In plain words
What is it for?
Running all tests, testing selected packages, running one named test, using race detection, and generating test coverage.
Why use it?
It standardises test commands for the whole project, selected packages, individual tests, or coverage reports, while showing failures clearly.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Install

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.

agentmods
npx agentmods add skills/usk6666/yorishiro-proxy/test
Any agent
npx skills add usk6666/yorishiro-proxy --skill test
Clone the repo
git clone --depth 1 https://github.com/usk6666/yorishiro-proxy

Made for: Claude Code.

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.

agentmods badge for test

README.md
[![agentmods](https://agentmods.dev/badge/skills/usk6666/yorishiro-proxy/test.svg)](https://agentmods.dev/skills/usk6666/yorishiro-proxy/test)
Your own site
<a href="https://agentmods.dev/skills/usk6666/yorishiro-proxy/test"><img src="https://agentmods.dev/badge/skills/usk6666/yorishiro-proxy/test.svg" alt="Measured on agentmods" height="20"></a>
Per session 3 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 209 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00003 $0.00209
Opus 5 $0.00002 $0.00105
Sonnet 5 $0.00001 $0.00042
Haiku 4.5 $0.00000 $0.00021

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

Security

Grade A, and why

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

.claude/skills/test/SKILL.md · 30 lines

What it actually says

/test

A skill for running Go tests.

Default Behavior

make test

Argument Patterns

  • /test — Run tests for all packages (make test)
  • /test ./internal/connector/... — Run specified packages only (make ensure-ui && go test -race -v ./internal/connector/...)
  • /test -cover — Run with coverage (make test-cover)
  • /test -run TestName — Run only a specific test (make ensure-ui && go test -race -v -run TestName ./...)

Steps

  1. Parse arguments
  2. If -cover is specified, run make test-cover
  3. If no arguments, run make test
  4. If a package or -run flag is specified, run make ensure-ui && go test -race -v <args>
  5. Display results and highlight any failures
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.

  1. 6d ago First seen · 30 lines · 3 tokens per session scan A 75828e0d1b7e

Subscribe to this mod's changes

test is a skill published in the GitHub repository usk6666/yorishiro-proxy (16 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 3 tokens to every session and 209 once invoked, about $0.0000 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-30.

Related

Other skills, from other repositories

go-rust-reverse

Use for reverse engineering stripped Go and Rust binaries including runtime recognition, pclntab/moduel data recovery, panic strings, and idiomatic decompilation recovery.

xAmirHamza77/ReverseOps-Skill · 38 tokens

go-check

Run go vet to analyze Go source code for suspicious constructs.

controlplaneio-fluxcd/flux-operator · 14 tokens

gopls-mcp

Semantic Go code analysis using gopls — type-aware definitions, references, implementations, call hierarchy, dependency graphs, and rename previews. Use these tools for semantic Go tasks; never fall back to grep — gopls sees types, scopes, and interfaces that text search misses.

xieyuschen/gopls-mcp · 62 tokens

bubbletea

Build terminal user interfaces with Go and Bubbletea framework. Use for creating TUI apps with the Elm architecture, dual-pane layouts, accordion modes, mouse/keyboard handling, Lipgloss styling, and reusable components. Includes production-ready templates, effects library, and battle-tested layout patterns from real…

devantler-tech/ksail · 63 tokens

golang-pro

Implements concurrent Go patterns using goroutines and channels, designs and builds microservices with gRPC or REST, optimizes Go application performance with pprof, and enforces idiomatic Go with generics, interfaces, and robust error handling. Use when building Go applications requiring concurrent programming…

devantler-tech/ksail · 95 tokens

go-best-practices

Go coding best practices. Use when writing or reviewing Go code. Covers error handling, concurrency, and idiomatic patterns.

Taoidle/plan-cascade · 30 tokens