tRPC-Agent-Go is a Go framework for building AI agent applications with language models, graph-based workflows, tools, memory, retrieval, evaluation, and observability. Go developers use it to create deployable agent systems that can integrate with A2A, AG-UI, and MCP. The catalogue add-ons provide reusable workflows and agent integrations for the framework.
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 trpc-group/trpc-agent-go --skill plan_routegit clone --depth 1 https://github.com/trpc-group/trpc-agent-goWrote 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/trpc-group/trpc-agent-go/plan_route)<a href="https://agentmods.dev/skills/trpc-group/trpc-agent-go/plan_route"><img src="https://agentmods.dev/badge/skills/trpc-group/trpc-agent-go/plan_route.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.00017 | $0.00182 |
| Opus 5 | $0.00009 | $0.00091 |
| Sonnet 5 | $0.00003 | $0.00036 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
plan_route 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 7d 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
plan_route
This skill is used by the dynamic structured output demo.
Output JSON Schema
{
"type": "object",
"properties": {
"route": {
"type": "string",
"description": "Route name"
},
"distance_km": {
"type": "number",
"description": "Distance in kilometers"
},
"eta_min": {
"type": "integer",
"description": "ETA in minutes"
}
},
"required": [
"route",
"distance_km",
"eta_min"
],
"additionalProperties": false
}
Commands
Print JSON result to stdout:
cat result.json
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.
- 7d ago First seen · 45 lines · 17 tokens per session scan A d58976196ad9
plan_route is a skill published in the GitHub repository trpc-group/trpc-agent-go (1,766 stars, last pushed today), licensed Apache-2.0. It adds 17 tokens to every session and 182 once invoked, about $0.0001 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.
Other skills, from other repositories
hephaestus-network
Use when the user types $hephaestus-network, /hep-network, or /agentlas-network, mentions @Hephaestus, or asks Agentlas to staff a durable goal from registered Local, owner Cloud, and public Hub agents or teams. The active host LLM staffs each turn; the exact roster remains goal-bound until explicit completion.
routing-card-authoring
Use whenever a build emits or repairs .agentlas/routing-card.json — the shared card contract for the single-agent builder, the team builder, and the packager. States what belongs in every field, which fields the hub can actually match on, and which fields silently break matching when a sentence leaks into them.
hep-storm
Run a force-robust Stormbreaker loop — route to real agents, execute a verified pipeline to completion.
hephaestus-upload
Use when the user types $hephaestus-upload, /hep-upload, or /agentlas-upload, or asks to upload, publish, or list an Agentlas agent or team. Ask Cloud (private) vs Agentlas Hub (public) FIRST, then publish through the bundled Hephaestus gate.
hep-graph
Build an Agentlas automation by describing it, list saved ones, or request a run.
hep-network
Staff a task from registered Local, owner Cloud, and public Hub agents.