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/konflux-ci/mintmaker/local-controller-testing-workflow-githubnpx skills add konflux-ci/mintmaker --skill local-controller-testing-workflow-githubgit clone --depth 1 https://github.com/konflux-ci/mintmakerWhat 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.00056 | $0.04125 |
| Opus 5 | $0.00028 | $0.02063 |
| Sonnet 5 | $0.00011 | $0.00825 |
| Haiku 4.5 | $0.00006 | $0.00413 |
Grade A, and why
local-controller-testing-workflow-github 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 — 433 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Local controller testing workflow
Self-contained — follow this skill only; ask the user for GitHub App credentials and test repo before bootstrap.
Overview
Run the MintMaker controller as a local process (make run on your machine) while using a real Kubernetes cluster for CRDs, Secrets/ConfigMaps, and Tekton workloads.
Important split:
- On your machine: controller (
make run),kubectl, and your editor/debugger. - In the cluster: Tekton
PipelineRuns, Renovate/OSV pipeline pods, and other in-cluster resources the controller creates.
The controller is not deployed into the cluster for this workflow.
Test YAML templates live in skills/local-controller-testing-workflow-github/assets/ — use those paths; do not rely on personal Desktop folders or other out-of-repo paths, unless instructed otherwise.
For AI agents — required before starting
Do not guess credentials or repository URLs. Ask the user for:
- GitHub App ID — numeric ID from GitHub App settings (not the client ID).
- GitHub App private key path — absolute path to the
.pemfile on the developer's machine.- The private-key path is only for substituting into the documented
kubectl create secret ... --from-file=...command. - Never Read, @-mention, or shell-cat that file.
- Never dump the resulting Secret with
-o yaml/-o json. - If something goes wrong with the secrets, stop and ask the user to run the
kubectlline themselves.
- The private-key path is only for substituting into the documented
- Test repository URL —
https://github.com/<owner>/<repo>.gitwhere that GitHub App is installed. - Git revision — branch or tag that exists in that repo (e.g.
main).
Confirm the user has created and installed the GitHub App (see GitHub App setup) if they have not done so already.
Optional follow-ups if the environment is unclear:
- Whether they are on Apple Silicon macOS (may need an amd64 VM — see below).
- Whether they already have a local cluster running (
minikube status/kind get clusters).
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 433 lines · 56 tokens per session scan A ccf7e26a0178
local-controller-testing-workflow-github is a skill published in the GitHub repository konflux-ci/mintmaker (5 stars, last pushed 3d ago), licensed Apache-2.0. It adds 56 tokens to every session and 4,125 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.
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…