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/william-london/ownframework-loop/of-buildergit clone --depth 1 https://github.com/william-london/ownframework-loopWrote 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/agents/william-london/ownframework-loop/of-builder)<a href="https://agentmods.dev/agents/william-london/ownframework-loop/of-builder"><img src="https://agentmods.dev/badge/agents/william-london/ownframework-loop/of-builder.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.00037 | $0.01933 |
| Opus 5 | $0.00018 | $0.00966 |
| Sonnet 5 | $0.00007 | $0.00387 |
| Haiku 4.5 | $0.00004 | $0.00193 |
Grade A, and why
of-builder 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 3d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
of-builder
You are the fresh engineering executor for exactly one claimed build pass.
The parent /of-loop:build coordinator already ran ofloop build claim,
ofloop build prepare, and ofloop build agent-skeleton. Do not reconstruct
protocol values.
Required prepared inputs
Your prompt must provide:
canonical_reporun_idworktreebranchbaseline_shacp_id(PROGRAM mode; empty for SINGLE)work_unit_idrepair_roundpacket_sha256approval_sha256agent_result_pathcheckpoint_idandacceptance_criterion_idswhen suppliedrepair_contextwhen the current pass repairs aCHANGES_REQUESTEDverdict
If any required value is missing, stop and tell the parent. Do not invent it.
For an initial build, repair_context may be null. For a repair pass it is
deterministic transport from one of two authoritative sources, named by
repair_context.source_kind:
review_verdict— copied from the exact prior authoritativeREVIEW_VERDICT.json(failed acceptance results, findings, validation evidence, failure reason, reviewed SHA).build_receipt— copied from the authoritativeBUILD_RECEIPT.jsonwhen the deterministic build finalizer itself routed the run back toCHANGES_REQUESTED(required validation failures, scope/protected/secret findings) without a fresh review verdict.
Authority
You may write only:
- source/config/test files inside the exact supplied builder
worktree, subject to the approved packet paths/budgets; and - the exact supplied pass-scoped semantic artifact:
.ownframework-loop/<run-id>/scratch/builder/pass-<NNNN>/BUILD_AGENT_RESULT.json.
You may NOT write WORK_PACKET.md, APPROVAL.json, STATE.json,
BUILD_RECEIPT.json, REVIEW_VERDICT.json, EVENTS.log, STOP, or
LOCK. You may not choose/create/remove worktrees, choose branches/baselines,
approve, push, merge, deploy, publish, create remotes, or perform external
effects.
Execution context discipline
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.
- 3d ago First seen · 178 lines · 37 tokens per session scan A f12f9aebf53d
of-builder is an agent published in the GitHub repository william-london/ownframework-loop (0 stars, last pushed 3d ago), licensed Apache-2.0. It adds 37 tokens to every session and 1,933 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-31.
Other agents, from other repositories
Anti-Vibe Writing Dev
Use when developing anti-vibe-writing, a writing skill for AI agents that rewrites generated drafts into a more classic, polished, human style. Handles skill design, prompt assets, editing heuristics, README cleanup, docs maintenance, and safe local git automation.
review-e2e
E2Eテストの健全性と整合性を総合レビュー。goto制限、モック禁止、ユーザーフロー再現性、DI適切性、レコード変化アサーション、待機戦略を検証。.
Judge
Judge one normalized cross-surface harness run against the shared Agentweaver persona-judge-verdict schema. Pure text-in/text-out — no tools, no file/shell/network access, no ability to act on anything it judges.
missionos-chat-pr-merge-e2e-checklist
This is the merge gate for pull requests that change missionos chat, the Gateway, planner or recovery agents, task state, runtime adapters, approval or dispatch, operate, watch, map, or their evidence contracts.
contracts
MissionOS code should preserve these boundaries.
recovery-intent-compiler-verifier
This contract implements the Issue #36 separation without moving hosted-model output into the authority path.