Borrowing it
Nothing to install: this file belongs to sevenschulte/agentic-harness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sevenschulte/agentic-harness/main/.claude/skills/save-memory/SKILL.mdgit clone --depth 1 https://github.com/sevenschulte/agentic-harnessWrote 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/sevenschulte/agentic-harness/save-memory)<a href="https://agentmods.dev/skills/sevenschulte/agentic-harness/save-memory"><img src="https://agentmods.dev/badge/skills/sevenschulte/agentic-harness/save-memory/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sevenschulte/agentic-harness/save-memory"><img src="https://agentmods.dev/badge/skills/sevenschulte/agentic-harness/save-memory.svg" alt="Reviewed on agentmods" width="80" 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.00074 | $0.00932 |
| Opus 5.5 | $0.00030 | $0.00373 |
| Sonnet 5.5 | $0.00015 | $0.00186 |
| Haiku 4.5 | $0.00007 | $0.00093 |
Grade A, and why
save-memory 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 2mo 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Save Memory
You are about to persist something learned in this session so it survives into future
sessions. This is the deliberate-write step that keeps memory/ current. Without
it, the files stagnate and the agent starts every session cold.
Memory files do not self-update. That's the whole point of this skill.
When to save
Save when one of these is true:
- The user explicitly says "remember X" / "save this" / "note for next time"
- A durable fact about the codebase, team, or user surfaced this session, something a fresh session would have to re-discover
- A preference or convention was decided (commit format, branch policy, test approach, naming convention) that isn't yet written down anywhere
- A project status changed (new project started, milestone hit, blocker resolved)
Do not save:
- Ephemeral state (current task progress, scratch directories, "where we are right
now"). Those belong in
ACTIVE.mdvia thewrap-upskill, not here. - The agent's own process narrative ("I ran 5 commands then..."). Save outcomes, not process.
- Secrets. Ever. Even if the user asks. Redirect to
.env.
Step 1 — Read what exists
If the project keeps a knowledge index (.claude/rules/knowledge-index.md or
similar), read it. It maps topics to files.
Otherwise, read memory/MEMORY.md and glob memory/**/*.md to see what's already
there.
Step 2 — Pick the right file
| If the fact is about... | Write it to... |
|---|---|
| Top-level identity, always-true facts about the user/product | memory/MEMORY.md |
| A preference or working-style rule | memory/preferences/<topic>.md |
| A specific project (status, decisions, architecture) | memory/projects/<name>/context.md |
| A research finding worth keeping | memory/research/<topic>.md |
| A codebase convention for a specific language/framework | memory/coding-standards/<language>.md |
Create new files only when the topic genuinely doesn't fit anywhere existing. One authoritative location per fact; pointers from elsewhere, never copies.
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.
- 2mo ago First seen · 112 lines · 74 tokens per session scan A 6246af172383
save-memory is a skill published in the GitHub repository sevenschulte/agentic-harness (2 stars, last pushed 6mo ago), licensed MIT. It adds 74 tokens to every session and 932 once invoked, about $0.0003 per session on Opus 5.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-31.
Other skills, from other repositories
lean-ctx
Use LeanCTX Context Gateway tools to select task-relevant code context, apply supported controls, reuse local knowledge and inspect recorded evidence. Use when lean-ctx MCP tools (ctx) are available or file, search or command output needs a focused view.
lean-ctx
Use LeanCTX Context Gateway tools to select task-relevant code context, apply supported controls, reuse local knowledge and inspect recorded evidence. Use when lean-ctx MCP tools (ctx) are available or file, search or command output needs a focused view.
automotive-engineer
Use when a task needs the judgment of an Automotive Engineer — computing weight transfer and tire friction-circle limits for a braking-while-cornering maneuver to set brake-force distribution, sizing a powertrain and gear ratio against a 0-60 mph acceleration target while checking traction versus power limits, sizing…
automotive-engineering-technician
Use when a task needs the judgment of an Automotive Engineering Technician — setting up and instrumenting test equipment (strain-gauge bridges, thermocouples, load/torque sensors) to an engineer's written test plan, selecting DAQ sample rate and an SAE J211 CFC filter class for a vehicle test channel, verifying…
aviation-inspector
Use when a task needs the judgment of an Aviation Inspector — determining whether an air carrier's fleet is in compliance with an Airworthiness Directive across a maintenance-records sample, deciding where the FAA's compliance-and-enforcement ladder places a finding (compliance action vs. Letter of Correction vs.…
calibration-technician
Use when a task needs the judgment of a Calibration Technologist/Technician — computing a Test Uncertainty Ratio (TUR) and deciding whether it meets the 4:1 target, building a measurement uncertainty budget (Type A/Type B, GUM-style) for a calibration, tracing a reference standard's chain of custody to NIST/SI…