Call ijfw_metrics to get counts and last-update timestamps for all tiers.
Scan .ijfw/memory/ for all .md files. For each, note:
File name, size (lines), last modified date.
Days since last referenced (use file mtime as proxy).
Categorize entries:
ACTIVE -- referenced within 30 days
STALE -- not referenced in 30-90 days
ARCHIVE -- not referenced in 90+ days, or flagged as superseded
Report:
MEMORY HEALTH REPORT
Total entries: <N> | Total size: ~<X> lines
Active: <N> | Stale: <N> | Archive candidates: <N>
STALE ENTRIES (>30 days unreferenced)
- <filename>: <one-line summary> [last seen: <date>]
ARCHIVE CANDIDATES (>90 days or superseded)
- <filename>: <one-line summary> [last seen: <date>]
RECOMMENDATION
Archive <N> entries to .ijfw/memory/archive/. No data is deleted.
Pruning question: for each entry flagged STALE or ARCHIVE, ask "Would removing this rule cause the agent to make a mistake?" If no, archive. If yes, keep and tighten. Memory that doesn't change behavior is bloat that crowds out memory that does.
Ask before acting:
Archive <N> stale entries? (y/n -- files move to .ijfw/memory/archive/, not deleted)
On confirmation, move flagged files. Store audit result:
ijfw_memory_store: memory audit on <date> -- archived <N> entries
1---2name: ferroxlabs-ijfw-ijfw3description: Execution4---56## Execution781. Call `ijfw_metrics` to get counts and last-update timestamps for all tiers.9102. Scan `.ijfw/memory/` for all `.md` files. For each, note:11 - File name, size (lines), last modified date.12 - Days since last referenced (use file mtime as proxy).13143. Categorize entries:1516```17ACTIVE -- referenced within 30 days18STALE -- not referenced in 30-90 days19ARCHIVE -- not referenced in 90+ days, or flagged as superseded20```21224. Report:2324```25MEMORY HEALTH REPORT26 Total entries: <N> | Total size: ~<X> lines27 Active: <N> | Stale: <N> | Archive candidates: <N>2829STALE ENTRIES (>30 days unreferenced)30 - <filename>: <one-line summary> [last seen: <date>]3132ARCHIVE CANDIDATES (>90 days or superseded)33 - <filename>: <one-line summary> [last seen: <date>]3435RECOMMENDATION36 Archive <N> entries to .ijfw/memory/archive/. No data is deleted.37```38395. **Pruning question:** for each entry flagged STALE or ARCHIVE, ask "Would removing this rule cause the agent to make a mistake?" If no, archive. If yes, keep and tighten. Memory that doesn't change behavior is bloat that crowds out memory that does.40416. Ask before acting:42 > `Archive <N> stale entries? (y/n -- files move to .ijfw/memory/archive/, not deleted)`43446. On confirmation, move flagged files. Store audit result:45 > `ijfw_memory_store: memory audit on <date> -- archived <N> entries`4647---48> Source: [FerroxLabs/ijfw](https://github.com/FerroxLabs/ijfw) — distributed by [TomeVault](https://tomevault.io).49<!-- tomevault:4.0:skill_md:2026-07-04 -->
Run npx skillmds@latest add tomevault-io/ferroxlabs-ijfw-ijfw 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.
Execution It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
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.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.
tomevault-io