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/konveyor/agentic-controller/executenpx skills add konveyor/agentic-controller --skill executegit clone --depth 1 https://github.com/konveyor/agentic-controllerWhat 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.00029 | $0.00457 |
| Opus 5 | $0.00015 | $0.00229 |
| Sonnet 5 | $0.00006 | $0.00091 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
execute 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
Execute Stage
Executes the migration by following the steps in docs/plan.md in order.
Startup
- Read
docs/plan.md
Execution Loop
Work through the steps in docs/plan.md in order.
For each step:
- Read the target file
- Apply the transformation described in the step
- Write the modified file
- Record step status as
applied - If the step cannot be applied (file missing, transformation impossible):
record step status as
failedwith the error, and continue to the next step
Write Output
You MUST complete this step.
Create .konveyor/handoff.md (make the .konveyor/ directory first if it does
not exist) and write an ## Execute section into it. This stage owns the creation
of the handoff file; later stages append their own sections to it.
Record the overall status, then one line per step from docs/plan.md — the step
id, the file touched, the action (MODIFY/CREATE/DELETE), the result
(applied or failed), and the error message for any failure.
## Execute
- Status: completed
| Step | File | Action | Result | Error |
|------|------|--------|--------|-------|
| 1 | src/main/java/... | MODIFY | applied | — |
| 2 | src/main/resources/application.properties | CREATE | applied | — |
| 5 | src/main/java/... | MODIFY | failed | <error message> |
Rules
- Follow the steps in
docs/plan.mdin order - Do NOT fix build errors — that is the verify stage's job
- Do NOT run tests — that is the verify stage's job
- Do NOT modify
docs/plan.md - You MUST create
.konveyor/handoff.mdwith your## Executesection before finishing
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 · 67 lines · 29 tokens per session scan A fce9228eea0c
execute is a skill published in the GitHub repository konveyor/agentic-controller (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 29 tokens to every session and 457 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…