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/runtime-detectornpx skills add krakend/claude-code-plugin --skill runtime-detectorgit 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.00024 | $0.00530 |
| Opus 5 | $0.00012 | $0.00265 |
| Sonnet 5 | $0.00005 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
runtime-detector 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 yesterday.
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
Runtime Detector
Purpose
Determines the correct way to execute KrakenD commands by detecting available runtimes and providing ready-to-use commands with the appropriate Docker image or native binary.
When to activate
- User asks to run/start/execute KrakenD: "run krakend", "start the gateway", "execute krakend"
- User mentions Docker commands for KrakenD: "docker run krakend", "which docker image"
- User asks how to run their config: "how do I run this", "start my config"
- User asks about KrakenD versions or images: "which version", "what image to use"
CRITICAL: Always Use Runtime Detection
NEVER invent Docker images or commands. Always follow this process:
- Call
detect_runtime_environmenttool with the config file path - Use the
recommendationsarray from the response (ordered by priority) - Use
command_templatefrom priority=1 recommendation - If Docker needed, use
recommended_imagefield for the image name
Common hallucinations to avoid:
- ❌
devopsfaith/krakend(outdated) - ❌
krakend:latestwithout checking - ❌
krakend/krakend:version(wrong format) - ✅ Use exactly what
detect_runtime_environmentreturns
What the tool returns
has_native_krakend: Whether native binary is installedhas_docker: Whether Docker is availablerecommended_image: Correct Docker image (e.g.,krakend:2.8orkrakend/krakend-ee:2.8)recommendations: Array of execution options withcommand_templateready to useis_enterprise: Whether config uses EE features
Example Interaction
User: "Run my krakend.json"
Response: Call detect_runtime_environment, then provide the command from command_template. Explain if using native or Docker and why.
Integration
- After
config-validatorvalidates successfully → Offer to run with this skill - After
config-buildercreates config → Offer to test run - If user needs to validate first → Hand off to
config-validator
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.
- yesterday First seen · 51 lines · 24 tokens per session scan A 46e38c71eed2
runtime-detector is a skill published in the GitHub repository krakend/claude-code-plugin (3 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 24 tokens to every session and 530 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…