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/dburkart/auto-engineer/context-resetnpx skills add dburkart/auto-engineer --skill context-resetgit clone --depth 1 https://github.com/dburkart/auto-engineerWrote 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/dburkart/auto-engineer/context-reset)<a href="https://agentmods.dev/skills/dburkart/auto-engineer/context-reset"><img src="https://agentmods.dev/badge/skills/dburkart/auto-engineer/context-reset.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.00048 | $0.00721 |
| Opus 5 | $0.00024 | $0.00360 |
| Sonnet 5 | $0.00010 | $0.00144 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
context-reset 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
context-reset
This skill is a reference document, not an executable action.
/compactand/clearare built-in Claude Code CLI commands — they cannot be invoked by theSkilltool from within a running session. Reading this skill brings the guidance into context so you can apply the right approach for the situation.
Why context accumulates
Each auto-engineer iteration reads playbooks, fetches issues, reads source files, runs sub-agents, and produces diffs. That context stays in the conversation window across iterations unless explicitly trimmed. After several cycles the window grows large, cache misses become expensive, and prior-cycle residue (old branch names, resolved bugs, superseded plans) can subtly corrupt decisions.
Three options
| Situation | Action |
|---|---|
| Normal end-of-cycle, session still healthy, just want to trim cost | /compact (built-in) |
| Prior cycles are actively corrupting decisions — Claude is replaying resolved issues or hallucinating old state | /clear (built-in), then restart auto-engineer with explicit --iteration N |
| Container run requiring a truly clean process (token ceiling hit, env/credential refresh needed) | scripts/restart-loop.sh --iteration N (run on the host) |
/compact — the default (auto-engineer step 10)
Summarises the conversation in place. The iteration counter, stop-reason history, and current PR state survive in the summary. This is why auto-engineer step 10 calls /compact rather than /clear — the ScheduleWakeup prompt carries --iteration N forward, but the surrounding rationale lives in the summary.
How to invoke: type /compact directly in the Claude Code CLI. It cannot be called from a skill or tool.
/clear — full wipe
Erases the entire conversation. Use only when context corruption is confirmed — you will lose the iteration counter and any uncarried state. After /clear, restart auto-engineer explicitly:
/auto-engineer --iteration <N>
How to invoke: type /clear directly in the Claude Code CLI.
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 · 57 lines · 48 tokens per session scan A f5ef10b8d3ed
context-reset is a skill published in the GitHub repository dburkart/auto-engineer (5 stars, last pushed 4mo ago), licensed BSD-3-Clause. It adds 48 tokens to every session and 721 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 skills, from other repositories
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
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…
auditing-subgroup-fairness
Audit an OpenMed NER or de-identification model for performance disparities across demographic subgroups (sex, age band, race/ethnicity when available) using openmed.eval.fairnessreport. Use when the user wants per-subgroup recall and leakage, wants to check whether de-identification under-protects a group, wants to…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
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…