Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/aks-builds/quality-skillsnpx agentmods add skills/aks-builds/quality-skills/grpc-testingWrote 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/aks-builds/quality-skills/grpc-testing)<a href="https://agentmods.dev/skills/aks-builds/quality-skills/grpc-testing"><img src="https://agentmods.dev/badge/skills/aks-builds/quality-skills/grpc-testing.svg" alt="Measured on agentmods" 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.00120 | $0.02630 |
| Opus 5 | $0.00060 | $0.01315 |
| Sonnet 5 | $0.00024 | $0.00526 |
| Haiku 4.5 | $0.00012 | $0.00263 |
Grade B, and why
grpc-testing scanned grade B with 1 finding 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 8d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
grpcurl -plaintext -d '{"id":"ord-1001"}' localhost:9090 example.orders.Orders/GetOrder How it starts
The opening of the file, as written. The whole thing — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gRPC Testing
You are an expert in testing gRPC services — unary and streaming RPCs, server reflection, in-process testing, load testing, and .proto schema management. Your goal is to help engineers write fast deterministic gRPC tests and avoid the patterns that bite teams new to protobuf. Don't fabricate gRPC library method names, buf commands, or .proto directives. When uncertain, point the reader to grpc.io for the language-specific docs.
Initial Assessment
Check .agents/qa-context.md (fallback: .claude/qa-context.md) before answering. Pay attention to:
- Server language(s) — Go, Java, Python, Node, C#, Rust, C++. gRPC's test patterns differ by language.
- Schema management — schemas live in
.protofiles. Are they in the same repo, a shared monorepo path, or a separate proto registry (Buf Schema Registry, internal artifact)? Generated code lives next to consumers. - Server reflection enabled? — server reflection lets
grpcurl/evansinterrogate a running service. Without it, you must provide.protofiles to the client. - Streaming usage — unary RPCs are the easy case. Server-streaming, client-streaming, and bidi-streaming each need different test shapes.
- TLS / mTLS — gRPC almost always runs over TLS in prod. Tests against insecure local gRPC may miss TLS-related bugs.
If the file does not exist, ask: language, schema location, streaming surface, TLS mode (insecure / TLS / mTLS).
Why gRPC needs its own approach
- It's not HTTP/JSON. Tools and patterns from REST don't transfer directly.
- Protobuf schemas are first-class. Schema evolution rules differ from JSON/OpenAPI.
- HTTP/2 streaming means you have four RPC shapes (unary, server-streaming, client-streaming, bidi). Each needs distinct tests.
- Error model is rich. gRPC status codes (
OK,NOT_FOUND,UNAVAILABLE, ...) plus typed error details viagoogle.rpc.Status. Asserting on string messages = fragile; assert on codes.
Layers of testing
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 248 lines · 120 tokens per session scan B 6f3bcc9cc8b7
grpc-testing is a skill published in the GitHub repository aks-builds/quality-skills (2 stars, last pushed 5d ago), licensed MIT. It adds 120 tokens to every session and 2,630 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 1 finding (sends data to an external url). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
api-testing
API testing checks a software service directly through its endpoints, using OpenAPI or Swagger documentation or automated test cases. It can produce and run scripts that test requests and responses.
test-case-writer
Use when someone asks to generate test cases, write test cases from a user story, create test cases from a BRD, design test cases from a mockup or wireframe, or produce a test case table from requirements.
api-tester
Test and document API endpoints - validate responses, check status, generate examples.
api-tester
A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.
xdto-validate
A validator for XDTO packages in 1C:Enterprise. It checks the package model, its metadata object, and its connection to the configuration.
endpoint-probe
Probes each major Agent Monitor API route — /api/stats, /api/analytics, /api/sessions, /api/pricing/cost, /api/workflows/runs, /api/cc-config/overview — and reports each one's HTTP status, latency, and response shape, flagging which are reachable. Use to verify a dashboard install is wired up correctly.