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 processmission/oh-my-qemu --skill qemu-workflowgit clone --depth 1 https://github.com/processmission/oh-my-qemuWrote 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/processmission/oh-my-qemu/qemu-workflow)<a href="https://agentmods.dev/skills/processmission/oh-my-qemu/qemu-workflow"><img src="https://agentmods.dev/badge/skills/processmission/oh-my-qemu/qemu-workflow/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/processmission/oh-my-qemu/qemu-workflow"><img src="https://agentmods.dev/badge/skills/processmission/oh-my-qemu/qemu-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00078 | $0.00855 |
| Opus 5 | $0.00039 | $0.00428 |
| Sonnet 5 | $0.00016 | $0.00171 |
| Haiku 4.5 | $0.00008 | $0.00085 |
Grade A, and why
qemu-workflow 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 10d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QEMU Workflow
Audit workflow
For non-trivial workspace writes, use a stable
.oh-my-qemu/<task-slug>/ directory and create only needed entries:
.oh-my-qemu/<task-slug>/
├── audit.md # Baseline, plan, decisions, evidence, verification, and gaps
├── commands.md # Redacted commands, working directories, and results
├── logs/ # Decisive build, test, runtime, or diagnostic logs
├── scripts/ # Intermediate documents, scripts, traces, and harnesses
└── output/ # Generated deliverables, dependencies, and non-QEMU binaries
Keep intermediate documents, scripts, and harnesses in scripts/; decisive
logs in logs/; and generated deliverables, third-party dependencies, and
non-QEMU binaries in output/. Keep QEMU builds under source-root
builds/build-<target>/. Record effective paths in audit.md.
Before writing audit artifacts or configuring QEMU in a Git worktree, add
.agents/, .oh-my-qemu/, and builds/ to the repository-local file from
git rev-parse --git-path info/exclude; preserve existing entries and avoid
duplicates. Never stage or commit those paths. Stage or commit source only when
the user explicitly requests it.
At handoff, reconcile git status --short with the baseline and verify the
excluded paths are absent. Report task and build directories, source changes,
pre-existing changes, and unresolved gaps.
QEMU upstream boundary
QEMU's official GitLab and mailing lists are upstream project channels. A
patch becomes an upstream contribution when sent to the mailing-list recipients
selected through MAINTAINERS; do not prepare or send agent-generated patches
for that submission. Local branches, commits, patch files, pushes, and pull
requests are not by themselves QEMU upstream contributions. Perform those Git
actions only when requested and follow the workspace's Git policy.
Run the workflow
- Plan. Read planning.md in full. Capture the
baseline, goal, scope, acceptance criteria, risks, and verification gates in
audit.md. Do not silently change acceptance criteria. - Record provenance. When the result depends on source revisions, toolchains, firmware, kernels, images, DTBs, root filesystems, or generated outputs, read provenance.md in full and record only the inputs that affect the claims being made.
- Work in small rounds. For source changes, multi-hypothesis debugging, or substantial validation, read iteration.md in full. Advance one coherent objective at a time and update the audit record before starting another.
- Verify and review. Run the narrowest relevant gate after each round. Preserve decisive logs, distinguish observation from inference, and use an independent review path when available. Fix blocking findings before claiming an acceptance criterion passed.
- Hand off. Classify the result as
PASS,FAIL, orINCONCLUSIVE. Summarize acceptance-criterion status, evidence paths, effective commands, source changes, policy limits, and unresolved gaps. Do not claim completion when evidence is missing.
What ships with it
4 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.
- 10d ago First seen · 72 lines · 78 tokens per session scan A 33fe1dccc33e
qemu-workflow is a skill published in the GitHub repository processmission/oh-my-qemu (57 stars, last pushed 1mo ago), licensed MIT. It adds 78 tokens to every session and 855 once invoked, about $0.0004 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-30.
Other skills, from other repositories
trace
Evidence-driven tracing lane that orchestrates competing tracer hypotheses in Claude built-in team mode.
smiles-validation
Strict SMILES validation, structural comparison, and modification verification. Catches invalid LLM-generated molecules.
social-physics-filter
Unified boundary enforcement, interpersonal diagnostic, and relational audit engine. Absorbs 40 psychology + 2 social protocols and all relationship case studies.
cnsplots
Create, revise, and troubleshoot publication-ready scientific plots in Python with cnsplots, including distribution, regression, heatmap, genomics, survival, set, flow, and multi-panel figures. Use when a user asks for cnsplots code, Cell/Nature/Science-style visualization, precise physical figure dimensions…
relax-dev-debug
Develop and debug the Relax reinforcement learning project. Use this skill whenever modifying code in the relax/ directory, or running remote training jobs on a Ray cluster for validation. Also use it when the user mentions training, debugging training runs, submitting Ray jobs, or fixing training errors.
anomaly-characterization
SOP: Describe and classify anomalous phenomena that existing theory cannot explain.