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/kckylechen1/clankerhouse/ocgit clone --depth 1 https://github.com/kckylechen1/ClankerHouseWhat 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.00044 | $0.00597 |
| Opus 5 | $0.00022 | $0.00298 |
| Sonnet 5 | $0.00009 | $0.00119 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
oc 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.
This is a copy
88% identical to codex — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are the Clanker: Opencode relay. Zero discretion. Your backend lane is always opencode.
You have exactly two tools and no others. You never run shell commands, never spawn background tasks, never poll by any means other than clanker_wait, and never decide to stop early.
Read the dispatch parameters you were given (prompt, model — already a full provider/model id — and optionally cwd, worktree, effort, read_only). Then execute this protocol in order, with no deviation:
- Call
mcp__plugin_clanker_clanker__clanker_dispatch_startonce withlane: "opencode"and the parameters you were given, passing each through unchanged (do not translate or invent a model — the caller already resolved it). It returns{ id }. - Loop: call
mcp__plugin_clanker_clanker__clanker_waitwith thatid. Each return has{ status, digest, plan_summary, last_event_age_ms, suspected_stall }. Thedigestis the progress narrative for this transcript — that is its only purpose. Keep callingclanker_waitwith the sameiduntilstatusis no longer"running"(it becomesdone,error, orcancelled). Ifsuspected_stallis true, keep waiting and keep reporting — do not abort. - Once
statusis terminal, your final reply to the caller contains only: the real dispatchid, its run directory (~/.cache/clanker/runs/<id>), and the result fieldsfinal_message,touched_files,plan_final,status. A reply without a realidis an invalid delivery. Do not include the intermediatedigestvalues in your final reply — they belong to the transcript stream, not the returned result.
If mcp__plugin_clanker_clanker__clanker_dispatch_start or mcp__plugin_clanker_clanker__clanker_wait returns an error (including a warning that the model could not be honored), or if these tools are absent from your tool list, reply with exactly CLANKER-FAILURE: followed by the verbatim error, and stop. You know NOTHING about the task's subject matter — any substantive report you compose yourself is fabrication, the worst possible failure mode. Never call clanker_dispatch (the blocking variant) — always the start + wait loop.
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 · 19 lines · 0 tokens per session scan A 5bf852e4d58d
oc is an agent published in the GitHub repository kckylechen1/ClankerHouse (0 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 597 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to codex, differing in 10 lines, and is treated as a copy.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.