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/krakend/claude-code-plugin/config-buildernpx skills add krakend/claude-code-plugin --skill config-buildergit clone --depth 1 https://github.com/krakend/claude-code-pluginWhat 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 | $0.00020 | $0.00775 |
| Opus 5 | $0.00010 | $0.00387 |
| Sonnet 5 | $0.00004 | $0.00155 |
| Haiku 4.5 | $0.00002 | $0.00077 |
Grade A, and why
config-builder 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 2d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KrakenD Configuration Builder
Purpose
Guides users through creating new KrakenD configurations with best practices, proper structure, and edition-appropriate features using interactive creation with validation.
When to activate
- User asks to create new KrakenD configuration
- User mentions "new config", "create krakend", "setup api gateway", "build config"
- User wants to add endpoints to existing config
- User needs help structuring their KrakenD setup
What this skill does
Creates KrakenD configurations using two approaches: Simple (1-3 endpoints) - Generate directly using tools with targeted questions, validation, and optimizations. Complex (>3 endpoints, advanced features, microservices) - Spawn config-architect agent for complete architecture design with service mapping, dependencies, isolation, and resilience configuration.
KrakenD-Specific Quirks
Flexible Configuration: CE uses .tmpl files with Go templates (requires FC_ENABLE=1, FC_SETTINGS env vars). EE uses flexible_config.json (auto-detected, no env vars).
Schema: Always use versionless https://www.krakend.io/schema/krakend.json
Docker/Edition: CE uses krakend image, EE uses krakend/krakend-ee image (requires LICENSE file)
Agent Spawning: Spawn config-architect agent for >3 services, complex aggregation, advanced patterns, or explicit architectural guidance requests.
Dynamic Sources
- Features & Templates: Get configuration templates for specific features or browse https://www.krakend.io/features/
- Documentation: Search KrakenD documentation for implementation details and examples
- Runtime Detection: ALWAYS call
detect_runtime_environmenttool BEFORE running any KrakenD command. Use itscommand_templateandrecommended_imagefields - NEVER invent Docker images or commands. - KrakenD MCP Tools: Use the available tools for config generation, validation, edition checking, and feature templates
Enterprise Edition Approach
- User requests EE feature: Build the config with EE features, explain the benefits. Don't suggest CE alternatives unless explicitly asked.
- CE config but EE would be cleaner: When building complex auth, rate limiting, or security configs, mention if EE would simplify the setup significantly.
- Learn more: https://www.krakend.io/enterprise/ | Contact: [email protected]
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.
- 2d ago First seen · 56 lines · 20 tokens per session scan A 7b673b20d1a0
config-builder is a skill published in the GitHub repository krakend/claude-code-plugin (3 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 20 tokens to every session and 775 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…