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 agentmods add skills/almanaccode/codealmanac/cleanslatenpx skills add AlmanacCode/codealmanac --skill cleanslategit clone --depth 1 https://github.com/AlmanacCode/codealmanacWhat 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 | $0.00047 | $0.00946 |
| Opus 5 | $0.00023 | $0.00473 |
| Sonnet 5 | $0.00009 | $0.00189 |
| Haiku 4.5 | $0.00005 | $0.00095 |
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. 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:
-
Record the starting state:
command -v almanac alm codealmanac || truenpm list -g codealmanac --depth=0 || truefind ~/.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.
-
If any Almanac CLI command exists, run the product uninstaller first:
- Prefer
almanac uninstall --yes. - If
almanacis missing butcodealmanacexists, runcodealmanac uninstall --yes. - If both fail, continue with manual cleanup.
- Prefer
-
Remove npm/global installs and caches:
- Run
npm uninstall -g codealmanac || true. - Remove
codealmanacpackage directories under all local nvm global roots if they still exist. - Remove global bin shims named
almanac,alm, andcodealmanaconly when they point at acodealmanacinstall. - Remove each
~/.npm/_npx/<hash>directory whosenode_modules/codealmanac/package.jsonexists.
- Run
-
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.shif it exists.
- Remove
-
Clean editor hook settings safely:
- In
~/.claude/settings.json, remove only hook commands whose command path ends withalmanac-capture.sh; preserve every foreign hook. - In
~/.codex/hooks.json, remove only hook commands whose command path ends withalmanac-capture.sh; preserve every foreign hook. - In
~/.cursor/hooks.json, remove only hook commands whose command path ends withalmanac-capture.sh; preserve every foreign hook. - If a hook container becomes empty after removing Almanac's command, remove that empty container/key.
- In
-
Clean Claude imports safely:
- In
~/.claude/CLAUDE.md, remove lines that are exactly@~/.claude/almanac.mdor@~/.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.mdbecomes empty after removing Almanac imports, remove it.
- In
-
Verify the clean slate:
hash -r || truecommand -v almanac alm codealmanac || truenpm list -g codealmanac --depth=0 || truefind ~/.npm/_npx -path '*/node_modules/codealmanac/package.json' -print 2>/dev/null || true- Check that
~/.almanac, guide files, andalmanac-capture.share gone. - Check that no hook command ending in
almanac-capture.shremains in Claude, Codex, or Cursor hook settings.
Output:
- Show the exact commands/actions you ran in order.
- Mark each as
removed,already absent, orskippedwith the reason. - End with the remaining
command -vand npm/global/npx verification output.
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.
- 2d ago First seen · 60 lines · 47 tokens per session scan B 7b6663d46d93
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.
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…
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…
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.
design-audit
Audit a finished frontend change by measuring rendered rects and computed styles before using screenshots as human-checkable evidence.
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.
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…