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 agentmods add skills/arianlopezc/trabuco/add-modulenpx skills add arianlopezc/Trabuco --skill add-modulegit clone --depth 1 https://github.com/arianlopezc/TrabucoWrote 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/arianlopezc/trabuco/add-module)<a href="https://agentmods.dev/skills/arianlopezc/trabuco/add-module"><img src="https://agentmods.dev/badge/skills/arianlopezc/trabuco/add-module.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.00061 | $0.00860 |
| Opus 5 | $0.00030 | $0.00430 |
| Sonnet 5 | $0.00012 | $0.00172 |
| Haiku 4.5 | $0.00006 | $0.00086 |
Grade A, and why
add-module 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 5d 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add a module to an existing Trabuco project
Flow
-
Detect project: call
mcp__trabuco__get_project_infowith the current working directory. If it doesn't return a Trabuco project (no.trabuco.json), tell the user this skill requires a Trabuco project and suggest/trabuco:new-projectinstead. -
Confirm current state: show the user what modules are currently installed and which provider/broker is in use. This is for their confirmation before additions.
-
Recommend if no argument: if the user didn't specify a module, call
mcp__trabuco__list_modulesand recommend based on gaps:- Has API but no SQLDatastore? → suggest SQLDatastore
- Has EventConsumer but no Events contracts module? → suggest Events
- Has Shared/API but no AIAgent? → suggest AIAgent if they're building user-facing services
- Etc.
Present the top 1–3 candidates with rationale.
-
Check conflicts: SQLDatastore and NoSQLDatastore are mutually exclusive — warn if the user is attempting a conflict.
-
Execute: call
mcp__trabuco__add_modulewith the chosen module. Confirm any broker/database sub-choices (e.g., Kafka vs RabbitMQ for EventConsumer). -
Post-add verification: call
mcp__trabuco__run_doctorto verify the updated project is structurally sound. Report any warnings. -
Next steps: tell the user what the new module brought in — new package structure, new POM dependencies, new generated files to customize, any new
/add-Xskills that became relevant inside the project.
Rules
- Never add a module without explicit confirmation when the project is large (>5 modules already present).
- Respect module dependencies. Some modules require others (e.g., EventConsumer needs Events; API and AIAgent both have Shared as a hard dependency now because the auth runtime utilities live in Shared). If the user picks a module with missing prerequisites, offer to add the prerequisite first —
add_moduleresolves them automatically but it's good to surface. - After adding API or AIAgent, remind the user that OIDC Resource Server scaffolding ships dormant. The app refuses to boot when
trabuco.auth.enabledis unset: operators must explicitly set it=false(local dev) or=trueplusOIDC_ISSUER_URIandOIDC_AUDIENCE(deployed). The validator catches the missing-decision case at boot rather than letting "no auth" become silent factory state. Seedocs/auth.mdfor the per-provider matrix. - After adding AIAgent, remind the user about: (1) A2A agent card at
/.well-known/agent.json(served dynamically byDiscoveryController, advertisesmcponly when MCP server is on); (2) MCP server is off by default —MCP_SERVER_ENABLED=trueto opt in, scope-gated bySCOPE_mcp:invokeonce enabled; (3) the legacyApiKeyAuthFilter(app.aiagent.api-key.enabled, default on) which now requires operator-populatedagent.auth.keys.*and refuses to boot with an empty key set. Demo keys live inapplication-local-dev.yml(SPRING_PROFILES_ACTIVE=local-devto load).
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.
- 5d ago First seen · 39 lines · 61 tokens per session scan A 9a5ff25c7cc6
add-module is a skill published in the GitHub repository arianlopezc/Trabuco (0 stars, last pushed 3mo ago), licensed MIT. It adds 61 tokens to every session and 860 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…