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 skills add konveyor/agentic-controller --skill verifygit clone --depth 1 https://github.com/konveyor/agentic-controllerWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/konveyor/agentic-controller/verify)<a href="https://agentmods.dev/skills/konveyor/agentic-controller/verify"><img src="https://agentmods.dev/badge/skills/konveyor/agentic-controller/verify/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/konveyor/agentic-controller/verify"><img src="https://agentmods.dev/badge/skills/konveyor/agentic-controller/verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00058 | $0.01200 |
| Opus 5.5 | $0.00023 | $0.00480 |
| Sonnet 5.5 | $0.00012 | $0.00240 |
| Haiku 4.5 | $0.00006 | $0.00120 |
Grade A, and why
verify 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 19d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify Stage
Builds the migrated project, fixes build errors until it compiles, then runs runtime verification to confirm the application actually starts and responds correctly. Grounds its work in the analysis results and the decisions the execute stage recorded. Does NOT re-execute migration steps.
Startup
- Read
docs/plan.md— find the Verification section for build, test, and blackbox commands - Read the
## Executesection of.konveyor/handoff.md— see which steps were applied or failed, and whether execution completed or was aborted - Read
.konveyor/analysis.json— the original violations, so you can confirm the migration addressed them - If execution was aborted or steps failed, log a warning but still attempt verification
Step 1 — Build Verification
Run the build command from docs/plan.md's Verification section.
- Build succeeds: record
build: "passed", proceed to Step 2 - Build fails: enter fix loop
Fix loop
For each build error:
- Read the error message to identify the file and issue
- Read the source file
- Apply a fix
- Never change business logic — if a fix would alter what the code does, record it and stop
- Never remove or stub out methods to make the build pass
Re-run the build after each round of fixes and keep going until it compiles — there is no limit on the number of rounds. Only stop early if an error genuinely cannot be fixed without changing business logic, and record it.
Step 2 — Tests
If a test command exists in the docs/plan.md's Verification section:
- Run the test command
- Record: passed count, failed count, total count
- Do NOT fix failing tests — document them
If no test command exists, record tests: "skipped".
Step 3 — Runtime Verification
If the build passed, run runtime checks. If the build failed, skip this step
and record runtime: "skipped".
3a. Start the application
Use the run command from the docs/plan.md's Verification section, or
detect it from the framework.
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.
- 19d ago Changed · +2 lines b55853347e19
- 2mo ago First seen · 147 lines · 58 tokens per session scan A bb0bb324adc2
verify is a skill published in the GitHub repository konveyor/agentic-controller (5 stars, last pushed 3d ago), licensed Apache-2.0. It adds 58 tokens to every session and 1,200 once invoked, about $0.0002 per session on Opus 5.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
4-phase root cause debugging: understand bugs before fixing.
observability-langsmith
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
reenable-test
Guide for investigating, fixing, verifying via TDD, and re-enabling disabled or flaky Chromium tests (C++, Android Java, or WebUI). Use this skill when asked to deflake, fix, or re-enable a disabled or flaky test case, or to verify post-submit stability of a re-enabled test. Don't use for disabling a failing test…
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.