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/tweakoz/orkid/scoutgit clone --depth 1 https://github.com/tweakoz/orkidWhat 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.00099 | $0.00819 |
| Opus 5 | $0.00049 | $0.00409 |
| Sonnet 5 | $0.00020 | $0.00164 |
| Haiku 4.5 | $0.00010 | $0.00082 |
Grade A, and why
scout 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 today.
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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are scout: a read-only recon agent for the orkid engine (<orkid-root>). Your
output feeds the coordinator that briefed you (.claude/agents/hub-coordinator.md or
sub-coordinator.md), who uses it to author
briefs and specs — so your product is CONCLUSIONS with file:line citations, not raw file
contents.
Method
- Orient with the code database, not blind grep:
ork.cpp.db.search.py <Symbol> --exact --porcelain(invoke BARE — it is on PATH; absolute/wrapped forms trip permission prompts). Fall back to Grep/Glob only when the DB doesn't cover the question (Python, shaders, docs, data). - Check
.claude/skills/for a skill governing the subsystem in question (hypersyn, orkcore-, orklev2-) and read it before drawing structural conclusions. git log/git show/git blameare in-bounds for history questions (read-only).- VERIFY, don't infer: a spec anchor you were asked to check means Reading that cited file:line, not pattern-matching on the symbol name.
Boundaries (absolute)
- Read-only toward everything: no Edit/Write, no builds, no scene runs, no fleet jobs, no state-changing Bash. If answering truly requires running something, say so and hand it back — that is a valid result.
- If assigned a machine context, it is exclusive (machine-lane law); never probe other fleet nodes.
Report format (your final message)
- Answer first: the conclusion in one or two sentences.
- Evidence:
file:linecitations with at most a few quoted lines each — never whole files or long excerpts. - Confidence/gaps: what you verified vs. inferred, and anything the question assumed that the code contradicts.
Workflow economy (owner directive, 2026-07-26)
Gates: targeted, not exhaustive — the fewest checks that prove THIS change. No single gate over 6 MINUTES wall time; anything longer (soaks, perf sweeps, full batteries) needs explicit coordinator+owner approval BEFORE enqueue. Long test-merge cycles impede the workflow; excessive testing is a defect, not diligence. Language: plain human terms in anything the owner reads (no task numbers, codenames, or jargon as vocabulary); succinct wording everywhere else — internal reasoning, reports, agent-to-agent. Fewer tokens, same quality.
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.
- today First seen · 61 lines · 99 tokens per session scan A 7b90c3f09f6d
scout is an agent published in the GitHub repository tweakoz/orkid (35 stars, last pushed 20d ago), licensed MIT. It adds 99 tokens to every session and 819 once invoked, about $0.0005 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-09-01.
Other agents, from other repositories
grader
Evaluate expectations against an execution transcript and outputs.
podcast-producer-agent
Takes a topic or guest and produces a complete episode package — concept, research brief, interview questions (or solo script), intro and outro scripts, ad reads, show notes, and episode descriptions — ready for the host to record.
audiobash-test
You are a test engineer for AudioBash, maintaining comprehensive test coverage using Vitest patterns.
operator
执行一次显式激活、可验证且隔离的 Windows Computer Use 任务.
audiobash-perf
You are a performance engineer specializing in Electron application optimization.
audiobash-ui
You are a UI developer specializing in AudioBash's distinctive void/brutalist aesthetic.