cleanslate

A cleanup workflow for removing Almanac and CodeAlmanac command-line tools and their related local files. It is intended to return the machine to the state of a first-time Almanac installation.

In plain words
What is it for?
Use it to check for and uninstall Almanac tools, remove their npm installations and caches, and clean up related configuration and hook files.
Why use it?
It helps remove old installations, caches, configuration files, and editor hooks without affecting unrelated files, packages, or integrations.

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/almanaccode/codealmanac/cleanslate
Any agent
npx skills add AlmanacCode/codealmanac --skill cleanslate
Clone the repo
git clone --depth 1 https://github.com/AlmanacCode/codealmanac

Made for: Claude Code, Codex.

Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 946 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00047 $0.00946
Opus 5 $0.00023 $0.00473
Sonnet 5 $0.00009 $0.00189
Haiku 4.5 $0.00005 $0.00095

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

Security

Grade B, and why

cleanslate scanned grade B with 1 finding 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

- In `~/.claude/settings.json`, remove only hook commands whose command path ends with `almanac-capture.sh`; preserve every foreign hook.
.agents/skills/cleanslate/SKILL.md · 60 lines

What it actually says

Almanac Clean Slate

Reset this machine to a first-time Almanac user state, then report exactly what changed.

Goal: remove every installed or cached codealmanac/Almanac CLI artifact from this laptop without touching unrelated user files, unrelated npm packages, or foreign editor hooks.

Work from safest to most direct:

  1. Record the starting state:

    • command -v almanac alm codealmanac || true
    • npm list -g codealmanac --depth=0 || true
    • find ~/.npm/_npx -path '*/node_modules/codealmanac/package.json' -print 2>/dev/null || true
    • Check for ~/.almanac, ~/.claude/almanac.md, ~/.claude/almanac-reference.md, legacy ~/.claude/codealmanac*.md, ~/.claude/hooks/almanac-capture.sh, ~/.codex/hooks.json, and ~/.cursor/hooks.json.
  2. If any Almanac CLI command exists, run the product uninstaller first:

    • Prefer almanac uninstall --yes.
    • If almanac is missing but codealmanac exists, run codealmanac uninstall --yes.
    • If both fail, continue with manual cleanup.
  3. Remove npm/global installs and caches:

    • Run npm uninstall -g codealmanac || true.
    • Remove codealmanac package directories under all local nvm global roots if they still exist.
    • Remove global bin shims named almanac, alm, and codealmanac only when they point at a codealmanac install.
    • Remove each ~/.npm/_npx/<hash> directory whose node_modules/codealmanac/package.json exists.
  4. Remove Almanac home/config artifacts:

    • Remove ~/.almanac.
    • Remove ~/.claude/almanac.md, ~/.claude/almanac-reference.md, ~/.claude/codealmanac.md, and ~/.claude/codealmanac-reference.md.
    • Remove ~/.claude/hooks/almanac-capture.sh if it exists.
  5. Clean editor hook settings safely:

    • In ~/.claude/settings.json, remove only hook commands whose command path ends with almanac-capture.sh; preserve every foreign hook.
    • In ~/.codex/hooks.json, remove only hook commands whose command path ends with almanac-capture.sh; preserve every foreign hook.
    • In ~/.cursor/hooks.json, remove only hook commands whose command path ends with almanac-capture.sh; preserve every foreign hook.
    • If a hook container becomes empty after removing Almanac's command, remove that empty container/key.
  6. Clean Claude imports safely:

    • In ~/.claude/CLAUDE.md, remove lines that are exactly @~/.claude/almanac.md or @~/.claude/codealmanac.md, plus those same lines followed by spaces/tabs and annotations.
    • Preserve lines that merely mention those paths inside other prose.
    • If CLAUDE.md becomes empty after removing Almanac imports, remove it.
  7. Verify the clean slate:

    • hash -r || true
    • command -v almanac alm codealmanac || true
    • npm list -g codealmanac --depth=0 || true
    • find ~/.npm/_npx -path '*/node_modules/codealmanac/package.json' -print 2>/dev/null || true
    • Check that ~/.almanac, guide files, and almanac-capture.sh are gone.
    • Check that no hook command ending in almanac-capture.sh remains in Claude, Codex, or Cursor hook settings.

Output:

  • Show the exact commands/actions you ran in order.
  • Mark each as removed, already absent, or skipped with the reason.
  • End with the remaining command -v and npm/global/npx verification output.
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 · 60 lines · 47 tokens per session scan B 7b6663d46d93

Subscribe to this mod's changes

cleanslate is a skill published in the GitHub repository AlmanacCode/codealmanac (990 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 47 tokens to every session and 946 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

ontology-bootstrap

Build a trustworthy first ontology from an empty or near-empty ontology-atlas vault using only Atlas MCP evidence. Use when the user asks to analyze a codebase, bootstrap/fill its ontology, extract product meaning from a repository, or when a requested ontology task finds only starter nodes. Separate observed…

wlsdks/ontology-atlas · 129 tokens

ontology-field-trial

Measure whether Atlas actually works on a repository nobody here knows, by building a vault with a real MCP agent and then handing that vault — without the source — to a second agent who must answer questions from it alone. Use when changing the construction rules, the MCP read/write contract, the bootstrap skill, or…

wlsdks/ontology-atlas · 112 tokens

design-build

Build UI from this repository's primitives and ramps in a deterministic order, then prove the rendered result with the matching instruments and gates.

wlsdks/ontology-atlas · 29 tokens

design-audit

Audit a finished frontend change by measuring rendered rects and computed styles before using screenshots as human-checkable evidence.

wlsdks/ontology-atlas · 26 tokens

design-council

Convene only the relevant Atlas design seats around a built surface, run independent critique and one cross-critique, then let design-guardian decide, apply, and remeasure.

wlsdks/ontology-atlas · 41 tokens

ontology-sync

After a code change, sync the project's ontology vault — read what's already there, identify new capabilities / elements / domains introduced by the change, and write them back via the MCP server (or fall back to the CLI). Use this at the end of any task that introduces a new feature, refactors a module, or renames a…

wlsdks/ontology-atlas · 90 tokens