Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/rjwalters/kicad-toolsnpx agentmods add skills/rjwalters/kicad-tools/repo-resetWrote 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/rjwalters/kicad-tools/repo-reset)<a href="https://agentmods.dev/skills/rjwalters/kicad-tools/repo-reset"><img src="https://agentmods.dev/badge/skills/rjwalters/kicad-tools/repo-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/rjwalters/kicad-tools/repo-reset"><img src="https://agentmods.dev/badge/skills/rjwalters/kicad-tools/repo-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.00030 | $0.02497 |
| Opus 5.5 | $0.00012 | $0.00999 |
| Sonnet 5.5 | $0.00006 | $0.00499 |
| Haiku 4.5 | $0.00003 | $0.00250 |
Grade A, and why
repo-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 5d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex form of the
/repo:resetcommand. Other commands appear as$repo-<verb>skills. Helper scripts and.claude/paths below are relative to the repository root and exist when the Claude Code surface is installed alongside this one.
$repo-reset — Back to Baseline
The end-of-task ritual: review and prune stale git state, sync with the remote, and land back on the default branch with a clean working tree. The reversible steps (fetch, land on the default branch) run by default; nothing irreversible — dropping a stash, deleting a branch or worktree — ever happens without an explicit opt-in and the permanent-loss check.
Usage
$repo-reset # Run the reversible baseline steps; keep all stashes, land on default
$repo-reset --ask # Confirm each step before acting
$repo-reset --prune # Also delete confirmed-safe branches/worktrees (after the loss check)
Two halves
The steps below split cleanly in two, and naming the split matters because callers can schedule the halves separately:
- Sync-and-switch (reversible — steps 1 and 4): the working-tree safety
check,
git fetch --all --prune, and landing on an up-to-date default branch. Nothing is removed. - Pruning (gated — steps 2 and 3): stash review and branch/worktree review. These can permanently remove work, so they keep the explicit opt-in and the [[branches]] permanent-loss check.
Run standalone, $repo-reset always runs all four steps in order, exactly as
documented — this split changes nothing here. It exists because [[all]] may run
the sync-and-switch half early (before its Docs stage) when the current
branch is fully pushed and behind the default branch, so that its doc stages
don't edit a stale checkout; the pruning half still runs last there, with its
gates intact.
Steps
1. Working tree safety check
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.
- 5d ago Changed · +5 lines 7ad84b344f71
- 8d ago First seen · 215 lines · 30 tokens per session scan A 6020a5a9ff40
repo-reset is a skill published in the GitHub repository rjwalters/kicad-tools (73 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 2,497 once invoked, about $0.0001 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-11-01.
repo-reset compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| repo-resetrjwalters/kicad-tools | Skill | 73 | yesterday | MIT | A | 30 | Claude Code, Codex |
| merge-batchdiegosouzapw/OmniRoute | Skill | 85k | yesterday | MIT | A | 46 | Claude Code |
| prowler-commitprowler-cloud/prowler | Skill | 15k | today | Apache-2.0 | A | 44 | Claude Code, Codex |
| gh-auth-isolationgithub/gh-aw | Skill | 5.6k | today | MIT | A | 20 | Claude Code, Codex |
| comet-githubrpamis/comet | Skill | 3.3k | yesterday | MIT | A | 72 | Claude Code, Codex |
| github-skillzeenie-ai/OpenCompany | Skill | 1.1k | 4d ago | MIT | A | 51 | Claude Code |
| re0-mergeLilMGenius/paperthin | Skill | 1.4k | yesterday | MIT | A | 70 | Claude Code |