grpc

grpc is a skill for Claude Code, Codex from Plazmodium/odin-workflow. It costs 30 tokens per session (3,196 once invoked), scanned A, original, MIT.

Guidance for building gRPC services, a way for programs to call functions on other programs, using Protocol Buffers to define messages and services.

In plain words
What is it for?
Writing .proto service definitions and producing server and client code for unary, server-streaming, and client-streaming calls.
Why use it?
It helps structure communication between microservices, including streaming, error handling, deadlines, and load balancing.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Writing .proto service definitions and producing server and client code for unary, server-streaming, and client-streaming calls.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/plazmodium/odin-workflow/grpc
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.

Any agent
npx skills add Plazmodium/odin-workflow --skill grpc
Clone the repo
git clone --depth 1 https://github.com/Plazmodium/odin-workflow

Made for: Claude Code, Codex.

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 grpc

README.md
[![agentmods](https://agentmods.dev/badge/skills/plazmodium/odin-workflow/grpc/github.svg)](https://agentmods.dev/skills/plazmodium/odin-workflow/grpc)
Your own site
<a href="https://agentmods.dev/skills/plazmodium/odin-workflow/grpc"><img src="https://agentmods.dev/badge/skills/plazmodium/odin-workflow/grpc/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.

agentmods 80×15 button for grpc

Your own site · 80×15
<a href="https://agentmods.dev/skills/plazmodium/odin-workflow/grpc"><img src="https://agentmods.dev/badge/skills/plazmodium/odin-workflow/grpc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,196 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00030 $0.03196
Opus 5.5 $0.00012 $0.01278
Sonnet 5.5 $0.00006 $0.00639
Haiku 4.5 $0.00003 $0.00320

Measured 1mo ago against content hash 7eb24ce0cedb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

agents/skills/api/grpc/SKILL.md · 555 lines

How it starts

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

gRPC High-Performance RPC

Instructions

  1. Assess the use case: gRPC excels at microservices, real-time streaming, and polyglot environments.
  2. Follow gRPC conventions:
    • Define services in .proto files
    • Use Protocol Buffers for serialization
    • Implement proper error handling with status codes
    • Consider streaming patterns
  3. Provide complete examples: Include proto definitions, server, and client code.
  4. Guide on best practices: Error handling, deadlines, load balancing.

Protocol Buffers

Basic Service Definition

// user.proto
syntax = "proto3";

package user.v1;

option go_package = "github.com/myorg/myapp/gen/user/v1";

import "google/protobuf/timestamp.proto";
import "google/protobuf/empty.proto";

// User service definition
service UserService {
  // Unary RPC
  rpc GetUser(GetUserRequest) returns (User);
  rpc CreateUser(CreateUserRequest) returns (User);
  rpc UpdateUser(UpdateUserRequest) returns (User);
  rpc DeleteUser(DeleteUserRequest) returns (google.protobuf.Empty);

  // Server streaming
  rpc ListUsers(ListUsersRequest) returns (stream User);

  // Client streaming
  rpc BatchCreateUsers(stream CreateUserRequest) returns (BatchCreateResponse);

  // Bidirectional streaming
  rpc Chat(stream ChatMessage) returns (stream ChatMessage);
}

// Messages
message User {
  string id = 1;
  string email = 2;
  string name = 3;
  Role role = 4;
  google.protobuf.Timestamp created_at = 5;
  google.protobuf.Timestamp updated_at = 6;
}

message GetUserRequest {
  string id = 1;
}

message CreateUserRequest {
  string email = 1;
  string name = 2;
  string password = 3;
  Role role = 4;
}

message UpdateUserRequest {
  string id = 1;
  optional string email = 2;
  optional string name = 3;
}

message DeleteUserRequest {
  string id = 1;
}

message ListUsersRequest {
  int32 page_size = 1;
  string page_token = 2;
  UserFilter filter = 3;
}

message UserFilter {
  optional Role role = 1;
  optional string search = 2;
}

message BatchCreateResponse {
  int32 created_count = 1;
  repeated string user_ids = 2;
}

message ChatMessage {
  string user_id = 1;
  string content = 2;
  google.protobuf.Timestamp timestamp = 3;
}

enum Role {
  ROLE_UNSPECIFIED = 0;
  ROLE_USER = 1;
  ROLE_ADMIN = 2;
  ROLE_MODERATOR = 3;
}

Read the full file on GitHub · 555 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.

  1. 1mo ago First seen · 555 lines · 30 tokens per session scan A 7eb24ce0cedb

Subscribe to this mod's changes

grpc is a skill published in the GitHub repository Plazmodium/odin-workflow (0 stars, last pushed 4mo ago), licensed MIT. It adds 30 tokens to every session and 3,196 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-01.

Related

Other skills, from other repositories

pipefy-api-fallback

Use this skill when a toolkit operation fails AND the introspection skill could not resolve the problem. This is the last-resort fallback (Tier 3): call the Pipefy GraphQL API directly using curl or httpx, authenticating with the Service Account (OAuth2) or a Personal Access Token (PAT) available as env var. Follow…

pipefy/ai-toolkit · 86 tokens

nornweave-api

Give AI agents their own email inboxes using the NornWeave API. Use when building email agents, sending/receiving emails programmatically, managing inboxes, retrieving threads, searching messages, or integrating with email providers (Mailgun, SES, SendGrid, Resend). NornWeave provides LLM-ready markdown parsing and…

DataCovey/nornweave · 77 tokens

user-usecases

Database of real user use cases for APIbase platform. Contains detailed examples of how specific APIs are onboarded, wrapped, and served to AI agents. Use this skill when you need to reference real integration examples, explain the APIbase onboarding process, or design new API wrappers based on proven patterns.

whiteknightonhorse/APIbase · 63 tokens

tray-multicd

API de Multi-CD (Centros de Distribuição) da Tray. Cobre o CRUD de centros de distribuição (/multicd/distribution-centers: listar, consultar, criar, atualizar e excluir CDs) e a gestão de estoque distribuído por CD (/multicd/stock/detailed/product/:id, /multicd/stock/detailed/variant/:id e PUT…

tray-tecnologia/tray-api-ai-plugin · 204 tokens

tray-status-pedido

API de Status de Pedido da Tray (recurso /orders/statuses). Cobre o CRUD completo do CATÁLOGO de status de pedido da loja: listar, consultar por ID, criar, atualizar e excluir tipos de status, definindo nome, descrição, cores hexadecimais (backgroundcolor/fontcolor) e o tipo de fluxo (type: open/closed/cancelled).…

tray-tecnologia/tray-api-ai-plugin · 155 tokens

tray-autorizacao

Autenticação e autorização na API da Tray. Utilize quando o desenvolvedor precisar implementar o fluxo OAuth 2.0, gerar chaves de acesso (accesstoken), renovar tokens expirados via refreshtoken, ou tratar erros de autenticação na plataforma Tray. Inclui o fluxo completo de 3 etapas, campos de resposta, tempos de…

tray-tecnologia/tray-api-ai-plugin · 80 tokens