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 agents/open-software-network/os-clovy/domaingit clone --depth 1 https://github.com/open-software-network/os-clovyWhat 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.00000 | $0.00742 |
| Opus 5 | $0.00000 | $0.00371 |
| Sonnet 5 | $0.00000 | $0.00148 |
| Haiku 4.5 | $0.00000 | $0.00074 |
Grade A, and why
domain 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain Docs
How the engineering skills should consume this repo's domain documentation.
This is a single-context repo: one glossary covers the React frontend
(src/), the Tauri shell (src-tauri/), and the clovy-api backend
(clovy-api/). There is no CONTEXT-MAP.md.
Before exploring, read these
CONTEXT.mdat the repo root — the canonical glossary / ubiquitous language. Glossary sections: Platform, Notes, Audio & recording, Agent runtime, AI work & billing, Desktop shell & updates, Clovy companion. The_Avoid_lines are binding. Its Flagged ambiguities section is the quick disambiguation table for the six overloaded terms: proxy, transcribe, credits, session id, "the model", channel — check it before naming anything.docs/adr/— read the ADRs touching the area you're about to work in. ADRs are append-only: supersede with a new ADR or dated addendum, never rewrite. Numbering: scan for the highestNNNN-*.mdand increment.
ADR routing by area
| Working on | Read first |
|---|---|
| Updater, releases, channels | 0001 (public releases repo), 0003 (rc channel + promotion) |
| Live transcript preview | 0002 (ephemeral, never source of truth) |
| Audio capture, sources, turns | 0004 (out-of-process system audio helper), 0005 (one WAV per source) |
| Agent harness, runtime protocol, sandboxing, sessions | 0038 (Clovy-owned OpenAI Agents SDK harness), 0039 (Routines and MCP) |
| Model picker, capabilities, pricing | 0007 (capabilities from live Venice catalog, never traits) |
| Image generation / editing | 0008 (/image fast path + LLM tools) |
| Clovy companion trust, native UI, pairing, relay, and mutation recovery | 0041-0048 (read the supersession chain through 0048) |
Don't conflate the three doc families
CONTEXT.md+docs/adr/— domain language and decisions (this file's scope).spec/— enforceable coding rules (sentence-case, no typographic dashes, central icons only, design tokens); violations fail review.specs/— Spec Kit feature specs;specs/003-conversation-turns/plan.mddoubles as the tech-stack reference.
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 · 60 lines · 0 tokens per session scan A 1507b3313de4
domain is an agent published in the GitHub repository open-software-network/os-clovy (357 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 742 tokens. 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 agents, from other repositories
demo-agents
We need a steady flow of demo videos — X/Twitter, Reddit, YouTube Shorts, blog posts, App Store-style screen recordings — and we'd like to scale that without scheduling Daniel to record every clip by hand. This doc maps the content-creation agent landscape, names the gap between "synthetic video hype" and "scripted…
qa-agents
Every quarter someone pitches an "AI does QA" tool. Most are web-first or mobile-first. MacParakeet is a menu-bar macOS app with a non-activating KeylessPanel overlay, global dictation hotkeys, and TCC-gated microphone/screen-recording flows. The general AI-QA frontier doesn't speak our shape yet. This doc tracks…
flow-verifier
Runs the VZT Flow end-to-end verification ladder (build, tests, TTS-transcribe checks, clean-test latency, paste-test, daemon socket checks, overlay states) and reports real measured numbers — never estimates. Use before claiming a change works, before a release, or when asked to verify VZT Flow.
flow-feature-builder
Implements VZT Flow features observing this repo's boundaries — additive edits, the gotcha list from CLAUDE.md, pull-rebase discipline in a shared worktree, never touching the user's running daily-driver app without relaunching it. Use for routine feature/bugfix work in this repo.
ai-systems-architect
Use as the cross-cutting AI/systems DESIGN authority to decide WHERE a seam goes across the Rust core, Angular FE, and brain — provider/model abstraction, agentic tool-use loop bounds, tool/ACI design, the egress-consent-redaction-ledger firewall, routing, context assembly, a new ingest source or consumption surface.…
adversarial-verifier
Anti-false-positive verifier for Murmur. Use AFTER a change is written, to TRY TO BREAK it — run the real gates (cargo test --lib / ng build / ng lint), live-reproduce in a browser against the zoneless Angular app with a mocked Tauri IPC, and hunt for the failure modes this app has actually shipped (sealed-content…