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/submit-prnpx skills add konveyor/agentic-controller --skill submit-prgit 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.00045 | $0.00835 |
| Opus 5 | $0.00023 | $0.00417 |
| Sonnet 5 | $0.00009 | $0.00167 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade A, and why
submit-pr 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Open a pull request that passes the two conventions enforced by
.github/workflows/pr-checks.yml: a valid emoji title prefix and a
changelog fragment when the change type requires one. Both are easy to
miss and will fail CI if wrong.
Work through the steps in order. Do not open the PR until the title prefix is chosen and (if required) the changelog fragment is committed.
1. Classify the change
Pick the single prefix that matches the change. Use the alias
(e.g. :bug:), never the emoji character.
| Prefix | Use for | Changelog fragment? |
|---|---|---|
:warning: |
Breaking change | required |
:sparkles: |
Non-breaking feature | required |
:bug: |
Patch / bug fix | required |
:book: |
Docs only | no |
:seedling: |
Infra, tests, chores, other | no |
:ghost: |
No release note wanted | no |
The title becomes <prefix> <concise summary>, e.g.
:sparkles: Add agent status reporting.
If the change spans categories, split it into separate PRs rather than picking a broader prefix — one logical change per PR.
2. Add a changelog fragment (if required)
For :warning:, :sparkles:, and :bug: PRs, CI requires a new file
in changes/unreleased/. Create it with the make target:
make changelog-create NAME=<pr-number-or-slug>-<short-description> KIND=<kind>
KIND must be one of: breaking, feature, enhancement, bugfix,
deprecation. Choose the kind that matches the prefix:
:warning:→breaking:sparkles:→feature(orenhancementif it improves existing functionality rather than adding new):bug:→bugfix
If you don't know the PR number yet, use a descriptive slug for NAME
now and rename the file after the PR is opened, or just keep the slug —
the filename only needs to be unique.
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 · 89 lines · 45 tokens per session scan A 329a859ebe51
submit-pr is a skill published in the GitHub repository konveyor/agentic-controller (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 45 tokens to every session and 835 once invoked, about $0.0002 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…