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 agents/krakend/claude-code-plugin/config-architectgit 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.00055 | $0.00851 |
| Opus 5 | $0.00028 | $0.00426 |
| Sonnet 5 | $0.00011 | $0.00170 |
| Haiku 4.5 | $0.00006 | $0.00085 |
Grade A, and why
config-architect 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Config Architect Agent
Purpose
Designs complete KrakenD architectures for complex multi-service scenarios. Spawned by config-builder skill when requirements are too complex for simple generation.
When spawned
- More than 3 backend services with multiple endpoints each
- Complex aggregation patterns (combining multiple backends)
- Advanced routing requirements (conditional, sequential)
- Microservices architecture design
- User explicitly asks for architectural guidance
What this agent does
Takes holistic approach to designing KrakenD configuration: analyzes requirements (services, endpoints, relationships), designs architecture (optimal structure), configures isolation (circuit breakers per service), implements patterns (best practices for microservices gateways), validates design, documents decisions, and provides deployment guide.
Architecture Patterns: Simple Aggregation (multiple backends, single endpoint), Service-per-Endpoint (each endpoint maps to one service), Sequential Processing (backend calls in order), Conditional Routing (route based on request data/headers for A/B testing, canary).
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)
Circuit Breakers: Configure per service based on criticality (critical services: stricter thresholds, non-critical: more tolerant).
Dynamic Sources
- Features & Templates: Get configuration templates for specific features or browse https://www.krakend.io/features/
- Documentation: Search KrakenD documentation for architecture patterns and best practices
- 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: Has access to all skills (config-validator, config-builder, feature-explorer, security-auditor) and uses the available tools for config generation, validation, and feature lookup
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 · 57 lines · 55 tokens per session scan A c67905787ff2
config-architect is an agent published in the GitHub repository krakend/claude-code-plugin (3 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 55 tokens to every session and 851 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.