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 skills add awrshift/agent-memory-kit --skill code-syncgit clone --depth 1 https://github.com/awrshift/agent-memory-kitWrote 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/awrshift/agent-memory-kit/code-sync)<a href="https://agentmods.dev/skills/awrshift/agent-memory-kit/code-sync"><img src="https://agentmods.dev/badge/skills/awrshift/agent-memory-kit/code-sync/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/awrshift/agent-memory-kit/code-sync"><img src="https://agentmods.dev/badge/skills/awrshift/agent-memory-kit/code-sync.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.00119 | $0.02096 |
| Opus 5.5 | $0.00048 | $0.00838 |
| Sonnet 5.5 | $0.00024 | $0.00419 |
| Haiku 4.5 | $0.00012 | $0.00210 |
Grade A, and why
code-sync 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 8d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/code-sync — documents reconciled against the repository
close-session reconciles the SESSION with memory. This reconciles a PROJECT's documents with
the CODE: every claim a spec still makes is checked against what is in the tree right now.
Two rails hold the whole skill up. Evidence, never a claim — a spec becomes done only from
a gate YOU ran in this session or a Verified cell someone already filled. Surgical edits
only — the only things you write are a status value, a Verified cell, one Stale since:
line, a map row, Last verified:, and a BACKLOG Done line. Everything else keeps its bytes.
Step 0 — locate the projects
Glob projects/*/README.md. If the repo keeps its documents elsewhere, read the rootCLAUDE.md/README.mdfor the docs home and use the map it names. Nothing found → say so and stop. This skill never scaffolds.- From each project README read two things: the map table ("Where this project's documents
live") — the SSOT for where plans, QA records and the backlog actually are — and the
**Workflow tier:**line, which sets how much evidence adoneneeds:
| Tier | Evidence a done needs |
|---|---|
prototype |
the gate output, run by you |
alpha |
+ an integrator acceptance walk named in the Verified cell |
beta |
+ a qa/qa-run-*.md record and tests naming each AC-n |
ga |
+ a review pass and a document entry for the change |
- The user named one project → sweep only that one. Otherwise sweep all of them.
Step 1 — inventory the specs
Read the header of every plans/*.md (**Created:** YYYY-MM-DD · **Status:** …; one grep over
the folder is enough). A plain Status: … line counts too, and a spec with no Created: takes its
date from a YYYY-MM-DD-<slug>.md file name — the SessionStart spec flags read them the same way.
A spec with no status line at all is counted as no status in the table, never guessed. Statuses are draft · decided · building · done · superseded · assumed · stale. Build the working table: spec · status · created · age in days.
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.
- 8d ago Changed da66248e354a
- 20d ago Changed · +2 lines 8aa021931a9f
- 27d ago First seen · 143 lines · 119 tokens per session scan A 3e90a0fbfb1c
code-sync is a skill published in the GitHub repository awrshift/agent-memory-kit (34 stars, last pushed 9d ago), licensed MIT. It adds 119 tokens to every session and 2,096 once invoked, about $0.0005 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-09-19.
Other skills, from other repositories
nav-pilot
Dispatch a Navigator task doc to Pilot as a labeled GitHub issue. Use when user says "dispatch TASK-XX to Pilot", "hand off to Pilot", "send to Pilot", or "queue for Pilot". One-way handoff (Navigator authors the spec, Pilot executes autonomously).
alive:create-walnut
Something new is emerging. A venture, an experiment, a person entering the orbit, a life area getting serious. It needs its own walnut — its own identity, history, and future. Scaffolds the full structure, maps existing context sources, and optionally migrates files across.
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.
alive-bundle
Create, manage, and graduate bundles -- the unit of focused work within a walnut.
alive-create
Scaffold a new walnut -- venture, experiment, person, life area, project.
alive-project
Regenerate now.json projections for all walnuts (mechanical, no approval needed).