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/plannpx skills add konveyor/agentic-controller --skill plangit 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.00066 | $0.01801 |
| Opus 5 | $0.00033 | $0.00901 |
| Sonnet 5 | $0.00013 | $0.00360 |
| Haiku 4.5 | $0.00007 | $0.00180 |
Grade A, and why
plan 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Stage
Analyzes the project deeply and writes a single migration plan for approval. The migration goal comes from the prompt. Does NOT modify any source files — planning only.
Inputs
.konveyor/analysis.json— Kantra rule violations and patterns, if present
Phase 1 — Analyze
1a. Read Prior Stage Outputs (if present)
- If
.konveyor/analysis.jsonexists, read it for rule violations and patterns
If it doesn't exist, derive the source stack and target directly from the prompt and the code.
1b. Understand the Project Architecture
Read the build manifest and walk the source layout to understand the project. Do this by reading files — do not build or execute the project.
- Build manifest (pom.xml, build.gradle, package.json, *.csproj, etc.): dependencies, modules/sub-projects, plugins, packaging type.
- Directory layout and layers: identify how the code separates into layers — data models/entities, services/business logic, controllers/API, persistence, configuration.
- Dependency flow: from imports and package structure, work out who depends on what (typically Models → Services → Controllers).
- High-risk abstractions: files that many others import, or that carry the most framework-specific patterns. Mark these as COMPLEX in the plan — changes here ripple across many files.
1c. Match Patterns to Files
Use the target's migration patterns to identify which files need migration. Check each file's imports, declarations, and configuration against the target's transformation rules to classify it:
- Simple (mechanical import or declaration replacement only)
- Complex (structural changes needed)
- Delete (file will be removed)
- Create (new file needed)
Use the analysis results as well: if .konveyor/analysis.json is present, each
incident pins a file, line, and message for a required change — cross-check
your classification against it and make sure every flagged incident maps to a step.
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 · 233 lines · 66 tokens per session scan A b19b12d38432
plan is a skill published in the GitHub repository konveyor/agentic-controller (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 66 tokens to every session and 1,801 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.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.