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 khalilbenaz/claude-skills-collection --skill grpc-service-designergit clone --depth 1 https://github.com/khalilbenaz/claude-skills-collectionWrote 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/khalilbenaz/claude-skills-collection/grpc-service-designer)<a href="https://agentmods.dev/skills/khalilbenaz/claude-skills-collection/grpc-service-designer"><img src="https://agentmods.dev/badge/skills/khalilbenaz/claude-skills-collection/grpc-service-designer/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/khalilbenaz/claude-skills-collection/grpc-service-designer"><img src="https://agentmods.dev/badge/skills/khalilbenaz/claude-skills-collection/grpc-service-designer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00104 | $0.02309 |
| Opus 5 | $0.00052 | $0.01154 |
| Sonnet 5 | $0.00021 | $0.00462 |
| Haiku 4.5 | $0.00010 | $0.00231 |
Grade A, and why
grpc-service-designer 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 9d 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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Concepteur de Services gRPC
Workflow en étapes
- Qualifier la communication — choisir le bon pattern (voir tableau ci-dessous) avant d'ouvrir un éditeur.
- Concevoir le contrat
.proto— package versionné, messages dédiés par RPC, enums avec valeur 0UNSPECIFIED. - Générer le code —
protocou plugin SDK ; vérifier que le code généré ne doit jamais être édité manuellement. - Implémenter serveur puis client — gestion d'erreurs gRPC status codes, deadlines, idempotence.
- Sécuriser et observer — TLS mutuel, intercepteurs logging/métriques, health checks.
- Valider la compatibilité — tester la rétrocompatibilité binaire avant tout déploiement.
Critère de choix du pattern de communication
| Pattern | Quand l'utiliser | Exemple concret |
|---|---|---|
| Unaire | Requête/réponse atomique, latence faible | CRUD, auth, paiement ponctuel |
| Server streaming | Serveur pousse un volume inconnu | Notifications, export CSV/JSON |
| Client streaming | Client envoie un flux puis attend le résultat | Upload fichiers, ingestion de logs |
| Bidirectionnel | Dialogue continu, ordre important | Chat temps réel, monitoring interactif |
Règle heuristique : si la réponse tient dans une seule trame TCP et que le serveur répond immédiatement → unaire. Dès qu'une des parties envoie plusieurs messages → streaming.
Conception du contrat Protobuf
Structure de référence
syntax = "proto3";
package myapp.payments.v1;
option csharp_namespace = "MyApp.Payments.V1";
option go_package = "github.com/myapp/payments/v1;paymentsv1";
import "google/protobuf/timestamp.proto";
service PaymentService {
// Unaire
rpc CreatePayment(CreatePaymentRequest) returns (CreatePaymentResponse);
// Server streaming
rpc WatchStatus(WatchStatusRequest) returns (stream PaymentStatusEvent);
// Client streaming
rpc BatchImport(stream ImportTransactionRequest) returns (BatchImportResponse);
// Bidirectionnel
rpc SyncLedger(stream LedgerEntry) returns (stream LedgerAck);
}
message CreatePaymentRequest {
string idempotency_key = 1; // UUID v4, obligatoire
int64 amount_cents = 2;
string currency = 3; // ISO 4217
string recipient_id = 4;
map<string, string> metadata = 5;
}
message CreatePaymentResponse {
string payment_id = 1;
PaymentStatus status = 2;
google.protobuf.Timestamp created_at = 3;
}
enum PaymentStatus {
PAYMENT_STATUS_UNSPECIFIED = 0; // obligatoire
PAYMENT_STATUS_PENDING = 1;
PAYMENT_STATUS_PROCESSING = 2;
PAYMENT_STATUS_COMPLETED = 3;
PAYMENT_STATUS_FAILED = 4;
}
// Champs supprimés → reserved, jamais effacés
// reserved 6, 7;
// reserved "old_field_name";
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.
- 9d ago First seen · 247 lines · 104 tokens per session scan A a4b765552fea
grpc-service-designer is a skill published in the GitHub repository khalilbenaz/claude-skills-collection (22 stars, last pushed 19d ago), licensed MIT. It adds 104 tokens to every session and 2,309 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
api-patterns
API design: naming, versioning, pagination, idempotency, OpenAPI, error contracts and safe retries. Triggers: API design, REST, GraphQL, OpenAPI, Swagger, error response, HTTP status, rate limit.
csharp-patterns
C#/.NET: LINQ, async/await, DI, records, nullable refs, ASP.NET Core, EF Core, MediatR. Triggers: C#, .NET, dotnet, ASP.NET, EF Core, LINQ, record type, IServiceCollection.
java-patterns
Java: Spring Boot, CompletableFuture, records, sealed types, JPA/Hibernate, virtual threads. Triggers: Java, Spring, JPA, Hibernate, Maven, Gradle, virtual thread, sealed class.
medplum-rules
Medplum (FHIR healthcare) coding rules: style, patterns, security, testing. Triggers: medplum.config.mts, medplum.config.ts, FHIR, Medplum, Bot, Subscription, Questionnaire.
api-design
REST API contract designer and reviewer. ALWAYS use when designing new endpoints, reviewing existing API contracts, planning API versioning, or standardizing error models. Covers resource modeling (URL/naming), HTTP method semantics, status code selection, error model consistency, pagination/filtering/sorting…
kafka-event-driven-design
Kafka event-driven architecture designer and reviewer, at the application/client layer. ALWAYS use when designing, reviewing, or troubleshooting how a service produces or consumes Kafka events — topic and partition-key design, producer and consumer client configuration, consumer group topology, event schema definition…