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 hainamchung/agent-assistant --skill fresh-contextgit clone --depth 1 https://github.com/hainamchung/agent-assistantWrote 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/hainamchung/agent-assistant/fresh-context)<a href="https://agentmods.dev/skills/hainamchung/agent-assistant/fresh-context"><img src="https://agentmods.dev/badge/skills/hainamchung/agent-assistant/fresh-context/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/hainamchung/agent-assistant/fresh-context"><img src="https://agentmods.dev/badge/skills/hainamchung/agent-assistant/fresh-context.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00029 | $0.01557 |
| Opus 5 | $0.00015 | $0.00779 |
| Sonnet 5 | $0.00006 | $0.00311 |
| Haiku 4.5 | $0.00003 | $0.00156 |
Grade A, and why
fresh-context 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 8d 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 — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fresh Context Subagent Pattern
Problem: Context rot degrades quality as session accumulates history.
Solution: Fresh isolated context per subagent dispatch.
When to Use
Dispatching subagent for implementation task?
↓ YES
FRESH CONTEXT PROTOCOL ← APPLY
Use when:
- Implementation tasks requiring isolated focus
- Multi-file changes where context pollution risk exists
- Quality-critical tasks requiring consistent reasoning
- Tasks where parent session history could mislead
Don't use when:
- Simple single-file edits (copy, rename, trivial changes)
- Quick lookups (read-only, no implementation)
- Context-independent tasks (no dependencies on session state)
Context Budget
| Task Type | Thinking Budget | Context Budget | Purpose |
|---|---|---|---|
| Implementation | ~20k tokens | ~200k tokens | Pure code generation |
| Review | ~15k tokens | ~50k tokens | Focused quality check |
| Research | ~10k tokens | ~100k tokens | Investigation tasks |
| Debug | ~15k tokens | ~80k tokens | Root cause analysis |
Dispatch Protocol
Pre-Dispatch Checklist
Canonical reference: See
rules/AGENTS.md— DELEGATION QUALITY CHECKLISTThis is the authoritative checklist. For quick reference:
□ Is runSubagent/Agent tool available? → TIER 1 (MANDATORY) □ Task complexity assessed? → Simple/Standard/Complex □ Specific file/directory boundaries assigned? □ Acceptance criteria explicit in spawn prompt? □ Subagent has MINIMAL context (not everything)? □ Reviewer is DIFFERENT from executor? □ File ownership is EXCLUSIVE (no conflicts)? □ Wave grouping planned if multiple parallel tasks? □ Token budget estimated for this phase? □ Mailbox path confirmed and writable? □ Confidence self-assessment completed?
Context Block Template
## SUBAGENT DISPATCH: {task_name}
### ISOLATED CONTEXT
{self-contained task description — what to do, NOT why}
### TARGET FILES
{file paths — exact locations to modify}
### ACCEPTANCE CRITERIA
1. {criterion_1 — verifiable outcome}
2. {criterion_2}
3. {criterion_n}
### CONTEXT ISOLATION
- NO parent session history
- NO previous attempts
- NO reasoning traces
- NO failed attempts
- Fresh context ONLY
### VERIFICATION STEPS
{how to verify task completion}
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.
- 8d ago First seen · 280 lines · 29 tokens per session scan A e21b83a66845
fresh-context is a skill published in the GitHub repository hainamchung/agent-assistant (54 stars, last pushed 3mo ago), licensed MIT. It adds 29 tokens to every session and 1,557 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…