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 commands/nguyenthienthanh/aura-frog/reset-sessiongit clone --depth 1 https://github.com/nguyenthienthanh/aura-frogWrote 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/commands/nguyenthienthanh/aura-frog/reset-session)<a href="https://agentmods.dev/commands/nguyenthienthanh/aura-frog/reset-session"><img src="https://agentmods.dev/badge/commands/nguyenthienthanh/aura-frog/reset-session.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.00000 | $0.01072 |
| Opus 5 | $0.00000 | $0.00536 |
| Sonnet 5 | $0.00000 | $0.00214 |
| Haiku 4.5 | $0.00000 | $0.00107 |
Grade A, and why
reset-session 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 4d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aura-frog:reset-session
Distill the active Epic (T2 Feature) into permanent_memory and offer to start a fresh session. Preserves history.jsonl, plan tree, conflict cache.
Usage
/aura-frog:reset-session # default: distill active Feature, prompt to reset
/aura-frog:reset-session --feature FEAT-007 # explicit feature ID (overrides active)
/aura-frog:reset-session --initiative INIT-001 # rare — distill at T1 level (quarterly use)
/aura-frog:reset-session --dry-run # show what would be distilled without writing
/aura-frog:reset-session --no-prompt # skip the reset confirmation (distill only)
Protocol (imperative)
- Resolve target. If
--featuregiven, use it. Else read.claude/plans/active.jsonand pickactive.feature. Refuse if neither (no active feature → nothing to distill). - Validate target status. Refuse if status is not
doneorarchived. Reset only triggers on completed Epics (per spec §19.1). - Refuse if epic-summarizer already ran. Check
history.jsonlforevent: epic_summarizedmatching this feature_id withrevision >= current.revision. If found, surface "already distilled" and skip to step 6 (reset prompt). - Invoke epic-summarizer agent via Agent dispatch. Pass: feature_id, prior permanent_memory.md state, trace files for the feature's tasks.
- Wait for distillation completion. epic-summarizer writes the new section to
.claude/memory/permanent_memory.mdand appendsevent: epic_summarizedto history.jsonl. - Show distilled section to the user (preview only — file is already written).
- Prompt: reset session? unless
--no-prompt. Show what's preserved vs. what's reset:- Preserved: history.jsonl, permanent_memory.md, plan tree, conflict cache, manual_overrides.md
- Reset (cleared): active conversation context, in-flight task buffers, scratch files
- On user
y/yes/reset:- Append
event: session_resetto history.jsonl - Update
.claude/plans/active.json— clearactive.task(andactive.storyif its parent feature was the one distilled), preserveactive.featureset to next pending Feature if any - Emit a control event hint to the runtime (e.g., suggest
/clearor new session start)
- Append
- On user
n/no/ silence:- Distillation stays (it's already written); only the reset is skipped
- Append
event: session_reset_declinedto history.jsonl
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.
- 4d ago First seen · 70 lines · 0 tokens per session scan A 2f8e4c8ac864
reset-session is a command published in the GitHub repository nguyenthienthanh/aura-frog (24 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,072 tokens. 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 commands, from other repositories
review-agentready
AgentReady-specific code review with attribute mapping and score impact analysis.
speckit.specify
Create or update the feature specification from a natural language feature description.
speckit.checklist
Generate a custom checklist for the current feature based on user requirements.
speckit.implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.tasks
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
speckit.clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.