How do I install the Attic Stats skill?

Run npx skillmds@latest add nishikantaray/attic-stats-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Attic Stats safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Attic Stats?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Attic Stats free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Attic Stats?

NishikantaRay (@nishikantaray) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Attic Stats by nishikantaray — Agent Skill

Name: Attic Stats
Author: NishikantaRay

Attic Stats

Report what the attic costs and what it holds, measured from local session transcripts. Use when the user asks "is the attic worth it", "attic stats", "how many tokens is this saving", "how big is the attic", or questions the plugin's value.

NishikantaRay Updated Sep 17, 2026

File contents

Attic stats

First, in the same shell command as anything below, locate the script:

ATTIC_JS=$(ls -d "${CODEX_HOME:-$HOME/.codex}"/plugins/cache/attic/attic/*/skills/attic/scripts/attic.js "${CODEX_HOME:-$HOME/.codex}"/skills/attic/scripts/attic.js "$HOME"/.agents/skills/attic/scripts/attic.js .agents/skills/attic/scripts/attic.js 2>/dev/null | sort -V | tail -1)

node "$(dirname "$ATTIC_JS")/../../../scripts/attic-stats.js"

Print what it reports. Then follow these rules when discussing it:

Lead with the verdict, not the contents. The user is asking whether this is worth keeping on. The What this means block answers that; the item counts do not.
If it says NOT EARNING ITS KEEP, say so first and plainly. Do not soften it or bury it under what the attic contains. Suggest /attic off, or ask what they were expecting to recall that they never did.
Never invent a savings percentage. The script deliberately produces none, because token spend depends on the task. Quote what is measured: index cost, citations, repeat file reads.
Two numbers carry the answer. Cited in replies is how often the model answered from the attic instead of re-reading. Repeat file reads is the share of reads that an earlier session had already done — the thing the plugin exists to reduce, so lower is better.
Early sessions look bad and that is expected. The session that writes pays; later sessions collect. If there is one session and no citations, say it is too early rather than implying failure.
If many items are past the injection budget, suggest /attic-pin for what must always be present and /attic-prune for what has gone stale.

Nothing leaves the machine: the script makes no network calls and sends no telemetry. Say so if the user asks.

---name: attic-stats-2description: Report what the attic costs and what it holds, measured from local session transcripts. Use when the user asks "is the attic worth it", "attic stats", "how many tokens is this saving", "how big is the attic", or questions the plugin's value.license: MIT---# Attic statsFirst, in the same shell command as anything below, locate the script:```bashATTIC_JS=$(ls -d "${CODEX_HOME:-$HOME/.codex}"/plugins/cache/attic/attic/*/skills/attic/scripts/attic.js "${CODEX_HOME:-$HOME/.codex}"/skills/attic/scripts/attic.js "$HOME"/.agents/skills/attic/scripts/attic.js .agents/skills/attic/scripts/attic.js 2>/dev/null | sort -V | tail -1)``````bashnode "$(dirname "$ATTIC_JS")/../../../scripts/attic-stats.js"```Print what it reports. Then follow these rules when discussing it:1. **Lead with the verdict, not the contents.** The user is asking whether this is worth keeping on. The `What this means` block answers that; the item counts do not.2. **If it says NOT EARNING ITS KEEP, say so first and plainly.** Do not soften it or bury it under what the attic contains. Suggest `/attic off`, or ask what they were expecting to recall that they never did.3. **Never invent a savings percentage.** The script deliberately produces none, because token spend depends on the task. Quote what is measured: index cost, citations, repeat file reads.4. **Two numbers carry the answer.** *Cited in replies* is how often the model answered from the attic instead of re-reading. *Repeat file reads* is the share of reads that an earlier session had already done — the thing the plugin exists to reduce, so lower is better.5. **Early sessions look bad and that is expected.** The session that writes pays; later sessions collect. If there is one session and no citations, say it is too early rather than implying failure.6. If many items are past the injection budget, suggest `/attic-pin` for what must always be present and `/attic-prune` for what has gone stale.Nothing leaves the machine: the script makes no network calls and sends notelemetry. Say so if the user asks.

Frequently asked questions