reset-baseline

A procedure for returning a project to a known clean state between agent runs or experiments. It checks uncommitted work before using Git, a tool for tracking code changes, and asks whether work should be saved or discarded.

In plain words
What is it for?
Use it before benchmark runs, after a failed experiment, or when you need a clean working tree and a verified test baseline.
Why use it?
It prevents leftover changes or failed experiments from affecting the next run, while avoiding accidental deletion of the developer’s work.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/danielvm-git/bigpowers/reset-baseline
Any agent
npx skills add danielvm-git/bigpowers --skill reset-baseline
Clone the repo
git clone --depth 1 https://github.com/danielvm-git/bigpowers

Made for: Claude Code, Codex.

Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 201 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00037 $0.00201
Opus 5 $0.00018 $0.00101
Sonnet 5 $0.00007 $0.00040
Haiku 4.5 $0.00004 $0.00020

Measured 2d ago against content hash 7db4c7bb5730, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

reset-baseline 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 2d 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.

.cline/skills/reset-baseline/SKILL.md · 22 lines

What it actually says

Reset Baseline

HARD GATE — Confirm with user before any destructive git operation. Never reset --hard without explicit approval.

Process

  1. git status — list uncommitted and untracked files.
  2. Ask: stash, discard, or keep each category.
  3. Safe defaults: git stash push -u -m "reset-baseline" for WIP; never force-push.
  4. Re-run setup-environment after reset.
  5. Run test baseline from kickoff-branch verify command.

Verify

→ verify: git rev-parse --git-dir >/dev/null 2>&1 && test -f skills/reset-baseline/SKILL.md

Changes

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.

  1. 2d ago First seen · 22 lines · 37 tokens per session scan A 7db4c7bb5730

Subscribe to this mod's changes

reset-baseline is a skill published in the GitHub repository danielvm-git/bigpowers (156 stars, last pushed 26d ago), licensed MIT. It adds 37 tokens to every session and 201 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-30.