Borrowing it
Nothing to install: this file belongs to processmission/oh-my-qemu. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/processmission/oh-my-qemu/main/AGENTS.mdgit 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/instructions/processmission/oh-my-qemu/agents-md)<a href="https://agentmods.dev/instructions/processmission/oh-my-qemu/agents-md"><img src="https://agentmods.dev/badge/instructions/processmission/oh-my-qemu/agents-md.svg" alt="Measured on agentmods" 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.00734 | $0.00734 |
| Opus 5 | $0.00367 | $0.00367 |
| Sonnet 5 | $0.00147 | $0.00147 |
| Haiku 4.5 | $0.00073 | $0.00073 |
Grade A, and why
oh-my-qemu AGENTS.md 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 8d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QEMU Skill Repository Agent Guide
This file governs development of this repository. It is not installed into QEMU. Each installed skill must contain its own runtime rules and must not depend on or cite this file.
QEMU upstream boundary
QEMU's official GitLab and mailing lists are upstream channels. A patch becomes
an upstream contribution only when it is sent to the mailing-list recipients
selected through QEMU's MAINTAINERS.
- Do not prepare or send agent-generated code or documentation for upstream
submission. Follow QEMU's current
docs/devel/code-provenance.rst. - Local branches, commits, patch files, pushes, and pull requests are not by themselves upstream contributions. Perform Git actions only when requested.
- Research, debugging, analysis, local experiments, verification, and workflow guidance are allowed.
Changes to this repository follow its local Git policy.
Skill rules
- Put skills in
skills/<skill-name>/SKILL.md. - Keep each skill independently installable. Do not depend on another skill, repository file, installer behavior, or plugin hook.
- Inside YAML frontmatter, put the Process Mission copyright and MIT SPDX
comments immediately after the opening
---and before the data fields. Keep data fields tonameanddescription. - Include matching
agents/openai.yamlwith quoteddisplay_name,short_description, and$skill-namedefault_prompt. - Keep
SKILL.mdconcise. Put long material in one-levelreferences/,scripts/, orassets/. - Do not require checkpoint commits. Stage or commit only when requested.
- Require explicit approval for external writes such as
gh issue create.
Every skill must include the compact audit contract. For a non-trivial task that writes to QEMU, use only the needed entries under:
.oh-my-qemu/<task-slug>/
├── audit.md
├── commands.md
├── logs/
├── scripts/
└── output/
Keep temporary tooling in scripts/, generated or third-party artifacts in
output/, and QEMU build output in a named source-root directory such as
builds/build-aarch64/—never build/ or task output/. Change source files
only when they are the requested deliverable.
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.
- 8d ago First seen · 80 lines · 734 tokens per session scan A e3eac2110f6d
oh-my-qemu AGENTS.md is an instructions file published in the GitHub repository processmission/oh-my-qemu (56 stars, last pushed 1mo ago), licensed MIT. It adds 734 tokens to every session, about $0.0037 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.