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 webbertakken/agent-skills --skill session-resetgit clone --depth 1 https://github.com/webbertakken/agent-skillsWrote 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/webbertakken/agent-skills/session-reset)<a href="https://agentmods.dev/skills/webbertakken/agent-skills/session-reset"><img src="https://agentmods.dev/badge/skills/webbertakken/agent-skills/session-reset/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/webbertakken/agent-skills/session-reset"><img src="https://agentmods.dev/badge/skills/webbertakken/agent-skills/session-reset.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.00092 | $0.00814 |
| Opus 5.5 | $0.00037 | $0.00326 |
| Sonnet 5.5 | $0.00018 | $0.00163 |
| Haiku 4.5 | $0.00009 | $0.00081 |
Grade A, and why
session-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 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session reset
Preserve session-specific state in PROMPT.md across a /clear, then restore afterwards.
PROMPT.md captures only session-specific state — current task, method, and progress. Persistent knowledge (user preferences, codebase patterns, dev quirks, workflow lessons) is handled separately by auto-memory and must NOT be included in PROMPT.md.
Workflow
1. Commit and push
Check git status for uncommitted changes. If there are any:
Security check — before staging, scan changed files for secrets. Flag and exclude any files matching
common sensitive patterns (.env*, *.key, *.pem, credentials.*, *secret*, *.token). Warn
the user if any are found and never stage them without explicit confirmation.
Then ask the user:
- Commit and push — stage safe changes, commit with a concise message, and push to the current branch
- Commit only — stage and commit without pushing
- Skip — leave changes as-is
If the user chooses to commit, use /commit. If they also want to push, push after the commit succeeds.
If the working tree is already clean, tell the user "Working tree is clean — nothing to commit." and move on.
2. Write PROMPT.md
Generate PROMPT.md at the project root by reviewing the current session state. PROMPT.md is ephemeral and must never be committed.
# PROMPT.md
## Current task
<!-- What we're working on - the goal, feature, or fix -->
## Method
<!-- Which workflow/approach is active (e.g. OpenSpec, manual, etc.) -->
<!-- Include any active change IDs, branch names, or tracking references -->
## Progress
<!-- Where we are in the process -->
<!-- What's done, what's in flight, what's next -->
<!-- Any blocking issues or open questions -->
Guidelines:
- Do NOT include user preferences, codebase patterns, dev quirks, or general knowledge — auto-memory handles that
- Do include task-specific context: current branch, active OpenSpec change, what's done, what's next, blocking issues
- Be specific and actionable — include file paths, branch names, change IDs, and concrete references
- Keep it concise — typically 20-40 lines
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 · 94 lines · 92 tokens per session scan A baaf1c0a1e66
session-reset is a skill published in the GitHub repository webbertakken/agent-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 92 tokens to every session and 814 once invoked, about $0.0004 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-31.
Other skills, from other repositories
apply
Use when applying accepted self-improvement sweep findings to skills as individually gated edits and commits.
what
Use when the user asks what is going on and needs a five-line summary of the session, branch, pull request, and ticket.
refocus
Use when a branch may have drifted from its ticket or pull-request goal and needs its work and gaps reclassified.
deslop
Use when cleaning AI slop, verbose commit messages, brittle references, or low-value changes from a branch before review.
situational-awareness
Use when you came back to a branch/PR: the work you were in the middle of, where it left off, repo state, and what reviewers ask or the PR waits on.
ratchet-files
Ratchet source file size so every file stays small enough for an agent to read whole: find every file over a token budget, split oversized files by concept, and set up the pre-commit ratchet that stops them from growing. Use when a commit is blocked because a file is over the size budget, when asked to find or split…