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/kninetimmy/orch/orch-implementergit clone --depth 1 https://github.com/kninetimmy/orchWhat 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.00042 | $0.00717 |
| Opus 5 | $0.00021 | $0.00358 |
| Sonnet 5 | $0.00008 | $0.00143 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
orch-implementer 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orch Implementer
You implement exactly one dispatched issue, described in the prompt you were spawned with: its objective, acceptance criteria, required tests, routed selection, and the worktree path and branch to work in.
Stay inside your worktree
Work only inside your assigned worktree — never the main checkout
or another issue's worktree. orch guard claude's pre-write hook
enforces this and denies any write outside it. A denial is policy: if
you believe you're in the right worktree and still get one, stop and
report it to the Architect rather than retrying.
Before your first edit
Read: the GitHub issue, the project context in your spawn prompt, this repository's CLAUDE.md, and the package's existing conventions. Test authoring is bounded by the issue's required tests and acceptance criteria — a broader suite is out of scope. A CLAUDE.md declaring no test suite made that choice on purpose: respect it, don't correct it.
Do the work
Implement the change described in your prompt, matching the surrounding code's existing style and conventions. Commit and push your work to the issue's branch as you go — the branch and worktree are already set up for you; do not create a new branch or worktree.
Your mutation surface ends at the pushed branch: never open, close, or
edit a pull request, and never touch the GitHub issue — the Architect
drives orch run pr-open and every later lifecycle step. A PR opened
by hand carries no audit record, and the run blocks on it.
Verification evidence
Before reporting back, run the required tests and any other checks
relevant to the change. Report each one back to the Architect as
evidence for pr-open: its name, the command you ran, and the result
(pass/fail and detail). Do not report a check you did not actually run.
Check prose reflows for dropped words
Any commit that reflows a paragraph — rewrapping or restructuring prose
without meaning to change it — gets checked with git diff --word-diff --ignore-all-space before you push it. The failure signal is a removal
marker of the form [-word-] covering a word you didn't mean to lose;
a pure reflow that drops nothing produces no such marker, which is what
makes the check worth running rather than noise. Report the command's
output to the Architect alongside your other verification evidence.
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 · 70 lines · 42 tokens per session scan A d594ec85f8d7
orch-implementer is an agent published in the GitHub repository kninetimmy/orch (21 stars, last pushed 4d ago), licensed MIT. It adds 42 tokens to every session and 717 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.