# Flaky Test Hunter — Run It on a jurniti MicroVM > Flaky test hunter for GitHub Actions: groups CI failures by test, scores flake vs real bug, drafts the quarantine or fix PR. You merge every change. Fork on… - Published: 2026-07-29 · Updated: 2026-07-29 · jurniti - Canonical: https://www.jurniti.com/blog/flaky-test-hunter-sf-template If GitHub Actions keeps going red for reasons that are not real bugs, this template earns its keep in recovered attention. **Flaky Test Hunter** is a public jurniti template (`/templates/flaky-test-hunter-sf`). You fork it into a paid **claudecode** microVM — not a Notion checklist and not a free shared sandbox. If you searched for **flaky test hunter agent**, this page maps that intent to a concrete fork: product truth, gates, BYOK, and the demo you should run before real customers see anything. ## What searchers mean by flaky test hunter agent People typing **flaky test hunter agent** usually want one of three things: a hire-me agency, a course, or a runnable operator. Hire-me pages sell retainers. Courses sell modules. jurniti sells a **running agent seat** you can fork, key, and operate — with Firecracker isolation and a human still on the hook for dangerous sends. This post is written for the third group: operators who will pay for a real box and own the demo. ## Why Flaky Test Hunter runs on a Firecracker microVM Laptop agents die when the lid closes. Docker density is not the same as multi-tenant isolation. jurniti provisions a Firecracker microVM per fork. The **claudecode** harness install lives on the platform golden path; your template persist (skills, instructions, config shapes) restores on top. Boot is fast; full provision is still about **three minutes**, not a marketing 124ms hand-wave for the whole journey. More on the harness: [claudecode guide](/blog/claude-code-hosting). Related gallery family: [Software Factory collection](/blog/software-factory-agent-templates). ## What you get when you fork Flaky Test Hunter When you fork **Flaky Test Hunter**, you are not buying a PDF. - The flaky-test-hunter skill, tuned for GitHub Actions failure triage - A vault stub at ~/vault/ci.md where you name your workflow - A demo prompt you can paste in your first five minutes - Your own copy in an isolated Firecracker microVM on your subdomain, still hunting after you close your laptop You still configure secrets after fork. Nothing valuable should be baked as a live credential in a public capture. ## The undeniable demo for flaky-test-hunter-sf From the template readme — **How the flaky test detection works**: 1. Fork the template, sign in to Claude Code, and export a GHTOKEN. 2. Put your workflow name in ~/vault/ci.md. 3. Paste: Last 20 failed runs of workflow CI. Report flakes. Draft only. 4. Read the report. Open the draft PR only if you agree with it. That is the whole loop. Draft-only by default. ## BYOK, human gates, and what you still own **BYOK:** model keys and third-party API keys are yours. jurniti does not mark up tokens in v1. Bring your own keys. Both stay inside your VM and never leave it: Secrets are scrubbed from the template. You supply your own. - Claude login or ANTHROPICAPIKEY - A GHTOKEN with access to Actions logs and draft PRs Where outbound mail, social publish, or paid fulfillment exists, treat **human approval** as product. Auto-spam is the wrong fit for this gallery. No free trial. No free tier. First purchase: **30-day money-back guarantee**. Model and SaaS fees stay on your accounts. ## Flaky Test Hunter vs building the same stack yourself | Path | What you get | Cost of time | | --- | --- | --- | | DIY scripts + laptop | Fragile glue | Nights and weekends | | Generic course | Concepts, no seat | Weeks of setup | | **Fork Flaky Test Hunter** | Pre-wired agent on microVM | Minutes to first demo | Courses do not remove wiring. Shared multi-tenant toys do not give you isolation. The template is the middle path: paid, isolated, opinionated. ## Fit and not-fit for flaky operators You, if CI red noise is drowning out real bug signal and reruns have become a ritual. Not you, if you want unattended merges into main. This agent drafts; it never merges. ## How to fork Flaky Test Hunter on jurniti 1. Open [Flaky Test Hunter](/templates/flaky-test-hunter-sf). 2. Fork on a paid plan. 3. Wait for the microVM (about three minutes). 4. Export BYOK keys listed in the About body. 5. Run the undeniable demo before real traffic. That is how **flaky test hunter agent** becomes an operated system instead of another bookmark. ## Frequently asked questions ### What is Flaky Test Hunter? Flaky Test Hunter is a public jurniti template. You fork it into a paid claudecode microVM with the agent setup already on disk. ### Who should search for flaky test hunter agent? Operators who want a runnable agent seat for this job — not only a course or a hire-me agency landing page. ### Is there a free trial? No free trial and no free tier. First purchase includes a 30-day money-back guarantee. Model and third-party fees are yours. ### Whose API keys? Yours (BYOK). Keys stay inside your microVM. jurniti does not proxy or mark up model tokens in v1. ### Which harness does Flaky Test Hunter use? claudecode. Choose another gallery template if you need a different agent runtime. ### How is this different from Zapier or a course? Zapier wires apps. Courses teach ideas. This template forks an always-on agent microVM with the workflow already installed. ### How long does provision take? About three minutes to a running microVM. Fast boot metrics are not the whole provision story.