Borrowing it
Nothing to install: this file belongs to a777ance/claude-code-homelab. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/a777ance/claude-code-homelab/main/.claude/commands/reseed.mdgit clone --depth 1 https://github.com/a777ance/claude-code-homelabWrote 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/a777ance/claude-code-homelab/reseed)<a href="https://agentmods.dev/commands/a777ance/claude-code-homelab/reseed"><img src="https://agentmods.dev/badge/commands/a777ance/claude-code-homelab/reseed.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.1 | $0.00033 | $0.00638 |
| Opus 5 | $0.00016 | $0.00319 |
| Sonnet 5 | $0.00007 | $0.00128 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
reseed 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 7d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Regenerate the working briefing mid-session without clearing the conversation — from the latest seed, not the copy pinned when the session opened.
The seed is this repo's briefing set (below); like a map seed, the whole working world
regenerates deterministically from it. But the seed is versioned and the founder pushes new
commits straight to main, so a "refresh" is really a pull: regenerating from a
behind-local seed just rebuilds a stale world. So this command pulls the current seed
first, then reseeds — the same sync-then-regenerate the SessionStart hook does around a
/clear, but for the no-clear case.
1. Pull the current seed onto disk (fast-forward only)
git fetch origin --quiet
git status --short # must be clean to fast-forward
git log -1 --format='local %h %ci %s' -- CLAUDE.md
git pull --ff-only 2>&1 # land origin/main on disk — no merge commit, no rewrite
git log -1 --format='now %h %ci %s' -- CLAUDE.md
- Dirty tree → do not pull. Stop and tell me what's uncommitted, so a fast-forward can't clobber in-flight work. Commit or stash first, then re-run.
- Non-fast-forward (local has diverged from
origin/main) → stop and tell me; don't force it. Reconcile by hand. - Already up to date → fine, the seed on disk is already current — continue.
2. Regenerate from the seed (read it all in one batch)
Read all of these from the now-current working tree, in parallel:
CLAUDE.md— the briefing (this repo is a setup guide, not a live system — don't deploy from here).README.md— start here.docs/ai-cto/context.md— current open items (AI CTO state).
These are the seed for this repo. Anything else is pulled on demand, not part of the standing seed.
3. Confirm ready — one line
Report exactly: the CLAUDE.md revision you landed (<short-hash> <date>), whether the
pull fast-forwarded or was already current, and that every seed file was read. Then
stop and wait for work. Do not summarize the seed back to me — just confirm the world is
regenerated from the latest seed.
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.
- 7d ago First seen · 49 lines · 33 tokens per session scan A bd13a621d738
reseed is a command published in the GitHub repository a777ance/claude-code-homelab (2 stars, last pushed 27d ago), licensed MIT. It adds 33 tokens to every session and 638 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-31.
Other commands, from other repositories
context
A project-context command that manages a .context directory containing decision notes, session logs, and history. It helps keep a record of why changes were made across Git branches and commits.
bm
Ask basemind anything about the current codebase — outlines, refs, callers, git history, blame, diffs, docs, memory.
context-load
Carga de contexto al inicio de sesión. Lee estado del workspace, decisiones recientes, último session save y actividad Git para arrancar con el big picture.
cache-invalidate
Invalidación selectiva de capas de caché con rollback seguro.
review-code
Read ALL memory bank code rules + best practices, check the files that changed, and APPLY fixes so they adhere. The active counterpart to /scan (which is read-only). Use after an AI session, before commit, to make changed files compliant.
vouch-propose-from-pr
Distill a merged PR into vouch claim proposals.