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/cluesmith/codev/builder-refreshnpx skills add cluesmith/codev --skill builder-refreshgit clone --depth 1 https://github.com/cluesmith/codevWhat 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.00081 | $0.01592 |
| Opus 5 | $0.00041 | $0.00796 |
| Sonnet 5 | $0.00016 | $0.00318 |
| Haiku 4.5 | $0.00008 | $0.00159 |
Grade A, and why
builder-refresh 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 yesterday.
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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/builder-refresh — save, clear, and come back knowing where you are
You are a builder that has reached a protocol boundary. Your context can be discarded
here safely, because everything that matters is already on disk: the spec, the plan,
status.yaml, your thread narrative, and git history. A fresh context re-orients from
those artifacts rather than from memory.
The enforcement is in the command, not in this document. afx self-refresh refuses to
clear on an unverified save, refuses when the re-entry cannot be scheduled, and refuses
when your worktree has uncommitted tracked changes. This skill sequences the steps and
explains the judgement calls; it cannot and does not decide whether the clear is safe.
When NOT to run this
Porch chooses the moment. You do not. Run this when porch's refresh task tells you to, or when the architect directs it. Do not invoke it mid-task on your own judgement — a boundary is a point a fresh context can resume from, and a mid-task snapshot resumes into confusion.
If you are not at a boundary and think you need a refresh anyway, say so to the architect
rather than doing it: afx send architect "...".
The procedure
1. Use the commands porch gave you
Porch's refresh task contains the exact two commands for this boundary, including the
--boundary flag. Run those, verbatim.
Do not retype them from memory and do not omit the flag. --boundary binds the challenge
to the boundary it was issued at, so a challenge left behind by an aborted refresh cannot
be used to clear you at a later boundary, against a save describing work that has since
moved on. That guard has been silently disabled twice by an instruction that dropped the
flag, which is why this document deliberately does not restate the commands.
If you arrived here without a porch task — an architect-directed refresh, say — there is no
boundary to bind, and the flagless form is correct. Run afx self-refresh --help for the
exact spelling rather than guessing it.
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.
- yesterday First seen · 139 lines · 81 tokens per session scan A d9e5fdf5dc54
builder-refresh is a skill published in the GitHub repository cluesmith/codev (286 stars, last pushed 5d ago), licensed Apache-2.0. It adds 81 tokens to every session and 1,592 once invoked, about $0.0004 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 skills, from other repositories
weather-fetcher
Instructions for fetching current weather temperature data for Dubai, UAE from Open-Meteo API.
time-skill
Display the current time in Pakistan Standard Time (PKT, UTC+5). Use when the user asks for the current time, Pakistan time, or PKT.
time-fetcher
Instructions for fetching current Dubai time via bash command.
weather-svg-creator
Creates an SVG weather card showing the current temperature for Dubai. Writes the SVG to orchestration-workflow/weather.svg and updates orchestration-workflow/output.md.
hns-lsel-curator
Local Self-Evolution Loop (LSEL) curator — the CLUSTER + drain engine for the GOOS-local PROPOSE→APPLY seam closure (SPEC-LSEL-LOCAL-EVOLUTION-001). Companion-offset drain of .moai/lessons-inbox.jsonl with a drain-side severity filter that drops the 65% Bash-timeout/sandbox noise, eventkey clustering with a frequency…
moai-foundation-core
Provides MoAI-ADK foundational principles including TRUST 5 quality framework, SPEC-First DDD methodology, delegation patterns, progressive disclosure, agent catalog reference, and token budget management (absorbed from moai-foundation-context). Use when referencing TRUST 5 gates, SPEC workflow, or context window…