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 instructions/larryxiao/openquack/agents-mdgit clone --depth 1 https://github.com/larryxiao/openquackWrote 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/larryxiao/openquack/agents-md)<a href="https://agentmods.dev/instructions/larryxiao/openquack/agents-md"><img src="https://agentmods.dev/badge/instructions/larryxiao/openquack/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 | $0.01328 | $0.01328 |
| Opus 5 | $0.00664 | $0.00664 |
| Sonnet 5 | $0.00266 | $0.00266 |
| Haiku 4.5 | $0.00133 | $0.00133 |
Grade A, and why
openquack 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 4d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
How AI agents (and humans) should contribute to OpenQuack. Most rules apply equally to both — humans can ignore the bits about advisor calls.
Posture
- Specs are the contract. Every PR cites a
SPEC-XXX. If no spec covers your change, write the spec first (one PR adds the spec; a follow-up PR implements). - Specs must include clear goals and how to validate them. Every spec's
## Acceptance criteriasection states what the feature is trying to achieve and exactly how to confirm it — a user-visible behaviour ("pastes within 200 ms of hotkey release"), a measurable metric ("WER ≤ 6.5 % on the noisy corpus"), or explicit manual steps a reviewer can follow. A spec without this is still a proposal; don't start implementation until the goal and its validation method are written down. - Atomic PRs. One spec, one milestone task. If your work touches multiple concerns, split it.
- Tests are non-optional. Touch a metric → bench delta documented in the PR. Touch logic → unit test added. Touch UX → the PR describes how to repro manually.
- Cite primary sources, not memory. When you need WhisperKit specifics, read
.build/checkouts/argmax-oss-swift/Sources/WhisperKit/Core/.... When you need bench math, readSources/OpenQuackKit/Metrics/. - Do the work, don't narrate it. PR descriptions describe the change and why, not what you tried.
Before you start
- Read
docs/VISION.md,docs/ROADMAP.md, this file. Skimdocs/BENCHMARKS.md. - Pick a 🔵 task in
ROADMAP.md. - Read the cited SPEC under
docs/SPECS/.
Workflow
- Open a draft PR early — even with just a one-line description and a stub change. Push small, test often.
- Run before pushing (use Xcode's toolchain; the system
swift 6.1.xlacks thePreviewsMacrosplugin thatKeyboardShortcutsdepends on, so a bareswift buildfails on a clean checkout):
CI uses the same toolchain, so the override matches reality.DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer swift build DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer swift test - If your change might affect transcription quality or latency, also:
and report the delta in the PR.DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer swift run openquack-bench --models tiny --corpus bench/corpus/short - Mark the PR ready for review when CI is green and your tests cover the change.
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.
- 4d ago First seen · 101 lines · 1,328 tokens per session scan A 79af0c8e0135
openquack AGENTS.md is an instructions file published in the GitHub repository larryxiao/openquack (52 stars, last pushed 3d ago), licensed MIT. It adds 1,328 tokens to every session, about $0.0066 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
macparakeet AGENTS.md
AGENTS.md instructions for moona3k/macparakeet, covering agents.md -- macparakeet, project shape, commands, worktrees and code boundaries.
macparakeet CLAUDE.md
Claude Code instructions for moona3k/macparakeet, covering claude.md, claude-specific rules, local-state cautions and references.
humla CLAUDE.md
Claude Code instructions for michaelwilhelmsen/humla, covering humla — project notes, what this app is, core capabilities, architecture overview and data flow during a recording.
os-clovy AGENTS.md
AGENTS.md instructions for open-software-network/os-clovy, covering clovy — agent instructions, project, os platform (shared brain), structure and domain & decisions — read before writing code.
humla AGENTS.md
AGENTS.md instructions for michaelwilhelmsen/humla, covering humla — project notes, what this app is, core capabilities, architecture overview and data flow during a recording.
cai CLAUDE.md
Instructions for cai-layer/cai, covering claude.md, what is cai?, design system, build & run and dev.