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 skills add alonf/specrew --skill specrew-refocusgit clone --depth 1 https://github.com/alonf/specrewWrote 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/skills/alonf/specrew/specrew-refocus)<a href="https://agentmods.dev/skills/alonf/specrew/specrew-refocus"><img src="https://agentmods.dev/badge/skills/alonf/specrew/specrew-refocus/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/alonf/specrew/specrew-refocus"><img src="https://agentmods.dev/badge/skills/alonf/specrew/specrew-refocus.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00166 | $0.01092 |
| Opus 5.5 | $0.00066 | $0.00437 |
| Sonnet 5.5 | $0.00033 | $0.00218 |
| Haiku 4.5 | $0.00017 | $0.00109 |
Grade A, and why
specrew-refocus 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 1mo 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
specrew-refocus
Type: Recovery + Discipline Skill Schema: v1 Status: Active drift-remediation surface (Feature 171)
Purpose
Re-load scoped Specrew methodology discipline into context ON DEMAND — the manual recovery surface for agent drift. Use it when context feels degraded: after a compaction, after a host restart, deep in a long session, or whenever you are about to act on methodology you are reconstructing from memory instead of from the source.
The same payload engine also fires AUTOMATICALLY: boundary syncs append the incoming stage's digest to their output (every host), and on hook-capable hosts, post-compaction and session-start events re-inject discipline without anyone asking. Treat any [specrew-refocus] block you see in tool output as binding stage discipline, not informational noise.
When to Use
- You notice drift: reviews going shallow, boundary discipline slipping, role rules fuzzy.
- A compaction or
/clearjust happened and the lifecycle position needs re-grounding. - You are entering a new lifecycle stage and want its discipline fresh (
--boundary <stage>). - You are diagnosing the refocus automation itself (
--status,--reset-breaker).
Invocation Contract
# All invocations run the project-local deployed engine:
pwsh -NoProfile -ExecutionPolicy Bypass -File .specify/extensions/specrew-speckit/scripts/refocus.ps1 [args]
| Arguments | Payload |
|---|---|
| (none) | always-true core + the CURRENT stage's discipline digest |
--boundary <stage> |
always-true core + the named stage digest (specify, clarify, plan, tasks, before-implement, implement, review-signoff, retro, iteration-closeout, feature-closeout) |
--role <name> |
the named role charter (e.g. reviewer, planner) |
--shape-catalog |
the Form-Without-Runtime-Compliance Shape catalog |
--everything |
the full digest corpus (heavy — warned) |
--compact-instructions |
a paste-ready /compact preserve-list built from live lifecycle state — use it at heavy-context boundary stops to compact at a clean watershed |
--status |
the whole operational truth: env kill switch, per-trigger catalog flags, per-session breaker state, injection-journal tail |
--reset-breaker |
clears tripped circuit-breaker flags for this project's sessions |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 57 lines · 166 tokens per session scan A 2776799e67a3
specrew-refocus is a skill published in the GitHub repository alonf/specrew (55 stars, last pushed yesterday), licensed MIT. It adds 166 tokens to every session and 1,092 once invoked, about $0.0007 per session on Opus 5.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
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
shellm
Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.