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 skills/william-london/ownframework-loop/specnpx skills add william-london/ownframework-loop --skill specgit clone --depth 1 https://github.com/william-london/ownframework-loopWhat 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.00030 | $0.01362 |
| Opus 5 | $0.00015 | $0.00681 |
| Sonnet 5 | $0.00006 | $0.00272 |
| Haiku 4.5 | $0.00003 | $0.00136 |
Grade A, and why
spec 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
94% identical to spec — 3 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.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OwnFramework Loop - spec
This skill is a host adapter over the deterministic ofloop core.
Rules
- Never approve your own packet.
- Never write STATE.json, APPROVAL.json, REVIEW_VERDICT.json, event logs, or lock files directly.
- Never manufacture the TTY confirmation token.
- Never add push, merge, deploy, publish, send, payment, or unrelated remote authority.
New specification (normal flow)
- Confirm the working directory is the target Git repository.
- Resolve repository identity BEFORE creating the run:
- inspect configured Git remotes;
- decide the packet classification from actual current state, not intended future state;
local_onlymeans no configured remote;- when a private GitHub review surface is part of the project, create/configure it, push the intended baseline, prove local/remote parity, and use
github_privatebeforeofloop spec new; - do not mint a local-only run and add a remote afterward.
- Inspect only enough repository context to draft an accurate bounded packet.
- Use ofloop spec new "" to create the run.
- Draft WORK_PACKET.md using the repository schema and packet conventions.
Inspect the project's declared package managers/toolchain and populate
network_read_allowlistonly with exact dependency/read domains the unattended BUILD/REVIEW may legitimately need after sealing (for exampleregistry.npmjs.org,pypi.org,files.pythonhosted.org). Omit or leave empty when dependencies are already provisioned. Never add a broad internet wildcard, scheme, port, path, publish endpoint, or unrelated host. - For PROGRAM packets with checkpoint-specific outcomes, keep the complete
mission acceptance contract at top level and assign it deterministically
with each checkpoint's
acceptance_criterion_ids. If any checkpoint uses scoped AC ids, every checkpoint must declare a non-empty list and the union must cover every top-level AC id. Do not usenot_applicablefor future checkpoint criteria merely to satisfy coverage. - Validate the packet shape with the supported validator.
- Return to the operator:
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 · 126 lines · 30 tokens per session scan A fdf98c687bdc
spec is a skill published in the GitHub repository william-london/ownframework-loop (0 stars, last pushed 2d ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,362 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to spec, differing in 3 lines, and is treated as a copy.
Other skills, from other repositories
economic-reasoning
Economic decision-making for agents in EconomySpace. Activate when the agent observes currency, prices, income, tax, or trading opportunities to make informed financial decisions.
to-issues
Decompose a PRD and/or SPEC into implementable, vertically-sliced Issues with real blocking edges, then create them in your chosen platform (GitHub or Local). Use after /prd (and optionally /prd-to-spec) to turn requirements into agent-ready tickets. Triggers on: create issues, to-issues, 创建issue, 拆解issue, 生成卡片, 创建卡片…
care.basic
Offer basic care check-ins for neighbors.
messaging.group
Send a concise practical group update.
bug-localization
Identify the precise location of bugs in source code, modules, and systems. Use this skill when debugging applications, investigating test failures, analyzing error reports, tracing runtime issues, or performing root cause analysis. Analyzes stack traces, error messages, failing tests, and code patterns to pinpoint…
code-comment-generator
Generates meaningful comments and documentation for code to improve maintenance and readability. Use when adding documentation to Python or Java code, including function/method docstrings, class documentation, inline explanations for complex logic, and code annotations (TODO, FIXME). Analyzes existing comment style in…