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/ackeskin/contexture/memory-auditnpx skills add AcKeskin/contexture --skill memory-auditgit clone --depth 1 https://github.com/AcKeskin/contextureWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/ackeskin/contexture/memory-audit)<a href="https://agentmods.dev/skills/ackeskin/contexture/memory-audit"><img src="https://agentmods.dev/badge/skills/ackeskin/contexture/memory-audit.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00068 | $0.04030 |
| Opus 5 | $0.00034 | $0.02015 |
| Sonnet 5 | $0.00014 | $0.00806 |
| Haiku 4.5 | $0.00007 | $0.00403 |
Grade A, and why
memory-audit 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
memory-audit
Sibling of review — same flow, but scoped to the memory tree (~/.claude/projects/<slug>/memory/) instead of code.
When to run
- User types
/memory-audit(explicit trigger). - User says "check my memory for drift," "audit my notes," "are there stale references."
- Scheduled run via
/schedule— weekly cadence is a natural fit (see "Schedule offer" below). - Do not auto-fire on session start, post-capture, or any hook. Mode A only.
Inputs
- Audit scope.
- Default:
~/.claude/projects/<current-project-slug>/memory/. Resolve the slug the same way discover does (Glob~/.claude/projects/*/memory/MEMORY.md, pick by project-root match). --project <slug>→ audit a specific other project's memory tree. Useful for cross-project hygiene.--check <dimension>→ run only one dimension (skip the others). Dimensions named below.
- Default:
- No content arguments — audit consumes the existing memory tree, not new content.
Procedure
1. Inventory the tree
Build the working set:
- Glob
<memory-root>/**/*.md— every memory file plus session-recaps. - Read
<memory-root>/MEMORY.md— the index. - For each memory file: parse frontmatter (
name,description,type,kind,scope,relevance,relations,superseded_by); capture the body's first paragraph for duplicate detection. Batch the Reads — independent files in one message, not one call per file. - For session-recap files (under
sessions/<date>-<slug>.md): parse filename and frontmatter only; bodies are not scanned for content checks.
Build maps:
path → frontmatterfor every file.MEMORY.md line → target pathfor every index entry.path → list of incoming relations(computed by reverse-walking every file'srelations:field — used for orphan detection in dimension 6).
If the inventory pass fails on any file (parse error, malformed frontmatter), surface that as the first finding under dimension 2 and continue with what parsed. Don't abort the whole audit because one file is broken.
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 · 239 lines · 68 tokens per session scan A 6dc1e1b05a15
memory-audit is a skill published in the GitHub repository AcKeskin/contexture (2 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 4,030 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
log-session
Append a structured entry to the project's session log (docs/LOGS.md): what was done this session, files touched, decisions taken, and the next step — so the next session (or another person) can pick up the thread without re-reading git history. Run it before /clear, before closing Claude Code, or at any natural…
context-scaffold
Analyzes an existing project and generates context files (AGENTS.md, context directory, cascading structure) pre-populated with discovered information. Run once to bootstrap, then customize.
AgentDB Memory Patterns
Implement persistent memory patterns for AI agents using AgentDB. Includes session memory, long-term storage, pattern learning, and context management. Use when building stateful agents, chat systems, or intelligent assistants.
V3 Memory Unification
Unify 6+ memory systems into AgentDB with HNSW indexing for 150x-12,500x search improvements. Implements ADR-006 (Unified Memory Service) and ADR-009 (Hybrid Memory Backend).
context-upgrade
Guides transition from your current context level to the next one -- minimal to full, full to cascading, or adding skills and hooks layers. Preserves existing content.
ReasoningBank Intelligence
Implement adaptive learning with ReasoningBank for pattern recognition, strategy optimization, and continuous improvement. Use when building self-learning agents, optimizing workflows, or implementing meta-cognitive systems.