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/melodic-software/claude-code-plugins/statelessnpx skills add melodic-software/claude-code-plugins --skill statelessgit clone --depth 1 https://github.com/melodic-software/claude-code-pluginsWhat 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.00140 | $0.01788 |
| Opus 5 | $0.00070 | $0.00894 |
| Sonnet 5 | $0.00028 | $0.00358 |
| Haiku 4.5 | $0.00014 | $0.00179 |
Grade A, and why
stateless 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-memory snapshot
bash "${CLAUDE_PLUGIN_ROOT}/skills/stateless/scripts/scope-report.sh" || echo "(snapshot unavailable — run the scope-report script manually)"
Stateless
Inspect and disable Claude Code auto memory, the store Claude writes for itself, one
directory per repo (~/.claude/projects/<project>/memory/, relocatable via
autoMemoryDirectory). Governs auto-memory only. Not in scope: CLAUDE.md / CLAUDE.local.md /
.claude/rules/ (use /claude-memory:audit), transcripts, history, or shell snapshots. For the
official full per-project wipe, use claude project purge (Claude Code v2.1.124+). What it does
and does not delete is quoted verbatim in
reference/official-guidance.md; the deletion plan and flags live
in the claude-directory doc.
Criteria and exact doc quotes live in reference/official-guidance.md; re-fetch the source pages listed there if a fact is load-bearing before you act.
Scope
| Entity | Location | This skill |
|---|---|---|
| Auto-memory store | ~/.claude/projects/<project>/memory/ (or autoMemoryDirectory) |
Yes. Status / disable / purge |
autoMemoryEnabled setting |
any settings scope | Yes. Reads and writes |
CLAUDE_CODE_DISABLE_AUTO_MEMORY |
OS env or settings env block |
Yes. Reads and writes |
CLAUDE.md / .claude/rules/ |
repo + user | No. Use /claude-memory:audit |
| CLAUDE.local.md | repo only, no user-scope equivalent | No. Use /claude-memory:audit |
| Transcripts | ~/.claude/projects/<project>/ |
No. Auto-cleaned by cleanupPeriodDays; claude project purge (v2.1.124+) deletes this project's now |
| Prompt history | ~/.claude/history.jsonl |
No. Persists indefinitely, not swept by cleanupPeriodDays; claude project purge filters this project's lines |
| Session files | ~/.claude/sessions/ |
No. One file per running session, cleared when the session exits rather than age-swept; not in claude project purge's deletion list |
| Shell snapshots / backups | ~/.claude/shell-snapshots/, ~/.claude/backups/ |
No. Swept by cleanupPeriodDays, but not project-scoped, so claude project purge leaves them untouched |
| Claude Desktop / claude.ai memory | server-side account | Direction only. See context/desktop.md |
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- context/desktop.md 1.6 KB
- context/disable.md 5.8 KB
- context/purge.md 9.5 KB
- context/status.md 3.7 KB
- evals/evals.json 5.0 KB
- reference/official-guidance.md 11 KB
- scripts/enumerate-all-projects.sh 2.8 KB runs code
- scripts/enumerate-all-projects.test.sh 3.4 KB runs code
- scripts/scope-report.sh 5.5 KB runs code
- scripts/scope-report.test.sh 4.5 KB runs code
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 · 103 lines · 140 tokens per session scan A ce294b1ae5c1
stateless is a skill published in the GitHub repository melodic-software/claude-code-plugins (12 stars, last pushed 2d ago), licensed MIT. It adds 140 tokens to every session and 1,788 once invoked, about $0.0007 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.
Other skills, from other repositories
deep-research
Conducts iterative deep research on any topic using web search, progressive exploration, and structured synthesis. Use when asked for comprehensive research, deep investigation, thorough analysis, or multi-source exploration of any topic. Triggers: research, investigate, deep dive, comprehensive analysis, explore…
error-ux
Principles and patterns for writing error messages that help users recover. Use when auditing, writing, or improving error messages in code. Triggers: error messages, user experience, error handling, exception messages, validation errors.
adversarial-patterns
Library of realistic adversarial attack vectors and anti-patterns to avoid. Contains examples of valid attacks and subtle gaming patterns to reject.
documentation-testing
Provides heuristics for identifying incomplete or broken documentation. Use when validating README setup instructions, testing onboarding flows, or auditing documentation quality. Triggers: docs, readme, onboarding, setup validation, documentation audit.
adversarial-analysis
Analyze code to identify explicit contracts, implicit usage patterns, and realistic boundary conditions. Contains concrete formulas for calculating input realism limits. Use before generating adversarial tests.
propagate-then-search
For constraint problems: eliminate impossibilities before guessing, reduce search space through inference, fail fast on contradictions.