agentmods.dev

build-memory

build-memory is a skill for Claude Code from SteveVitali/agent-skills. It costs 101 tokens per session (2,368 once invoked), scanned A, original, MIT.

A shared record system for multi-session software builds, stored in a repository under documentation folders. It defines templates, status records, decision records, validation, and migration from an older scratch layout.

In plain words
What is it for?
Use it to initialise or validate build records, migrate legacy scratch files, and provide the shared state used by build planning and implementation tools.
Why use it?
It keeps separate coding sessions aligned and leaves a committed, checkable history of what the build needs, decided, and completed.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions AGENTS.md.

Part of the agent-skills plugin — 11 skills shipped together

not rated 12repo +3 yesterday A scan 101 tokens original MIT

Good fit Use it to initialise or validate build records, migrate legacy scratch files, and provide the shared state used by build planning and implementation tools.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/stevevitali/agent-skills/build-memory
View source ↗ SteveVitali/agent-skills
Install

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.

Any agent
npx skills add SteveVitali/agent-skills --skill build-memory
Clone the repo
git clone --depth 1 https://github.com/SteveVitali/agent-skills

Made for: Claude Code.

Or install agent-skills, the plugin that ships this one along with the rest of its 11 skills.

Wrote 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.

agentmods badge for build-memory

README.md
[![agentmods](https://agentmods.dev/badge/skills/stevevitali/agent-skills/build-memory/github.svg)](https://agentmods.dev/skills/stevevitali/agent-skills/build-memory)
Your own site
<a href="https://agentmods.dev/skills/stevevitali/agent-skills/build-memory"><img src="https://agentmods.dev/badge/skills/stevevitali/agent-skills/build-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.

agentmods 80×15 button for build-memory

Your own site · 80×15
<a href="https://agentmods.dev/skills/stevevitali/agent-skills/build-memory"><img src="https://agentmods.dev/badge/skills/stevevitali/agent-skills/build-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 101 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,368 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00101 $0.02368
Opus 5 $0.00051 $0.01184
Sonnet 5 $0.00020 $0.00474
Haiku 4.5 $0.00010 $0.00237

Measured 2d ago against content hash 421c9d27aae3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

build-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 2d ago.

The scan reads SKILL.md. This mod also ships 6 executable files (scripts/adr-index.sh, scripts/check-build-memory.sh, scripts/memory-root.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/build-memory/SKILL.md · 179 lines

How it starts

The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Build Memory

The owner of the build-memory layer that decompose-spec, orchestrate-build, implement-spec, synthesize-spec and reconcile-build all read and write. It owns one contract file, one set of templates, one validator and one migration tool, so build memory is defined in exactly one place.

Precedent. agent-docs owns the shared Doc Authoring Guidelines other skills cite; build-memory owns the layout the same way. The contract is layout.md — the tree, the modes, the machine-state ledger, the manifest / ticket / marker / tail shapes, the deferrals / ADR / index / gate rules, who writes what, the validator, and the compatibility policy. Read it before any mode below; every other skill cites it and does not restate the tree.

Build memory is committed (the record of a multi-session build is audit-valuable and git is the artifact store); only regenerable bulk (logs/) is gitignored. A repo opts in with the marker <!-- build-memory: v2 --> in docs/build/README.md. A repo without it runs in legacy scratch mode — byte-for-byte the pre-0.2.0 behaviour (see layout.md § Compatibility and README.md).

Resolve the root first (every mode)

// turbo

bash scripts/memory-root.sh            # prints: mode=<committed|scratch>  root=<abs path>

Committed mode → the root is <worktree>/docs/build, resolved from the current worktree (a sibling build worktree reads its own chain tip). Scratch mode → the legacy gitignored dir. $BUILD_MEMORY_ROOT overrides both.

Mode: check (default)

Validate the layout. Read-only; exit-code gated; runnable in CI.

// turbo

bash scripts/check-build-memory.sh .    # exit 0 clean · 1 violations · 2 not a build-memory repo

It checks everything the skills derive (layout allowlist + logs/.gitignore; ticket filename grammar + unique sequence; manifest ↔ files both ways; backward Depends on; skeletons carry no run line; markers referenced; DEFERRALS ids unique + valid statuses; no OPEN row past a PASSED gate; ADR files ↔ generated index; every ADR has ## Revisit trigger; spec ADR appendix == file set when present; LEDGER.md key set + order and nextTicket; PHASE-LOG "done" ↔ BUILD_INDEX row + runs/<ID>.md; REQ→ticket coverage when the spec and req_id_pattern resolve; size + secret scans). The human summary lists each violation; the JSON at /tmp/build-memory-check.json mirrors it. A failure is a real block — the caller does not proceed past it.

Read the full file on GitHub · 179 lines

Files

What ships with it

60 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 2d ago First seen · 179 lines · 101 tokens per session scan A 421c9d27aae3

Subscribe to this mod's changes

build-memory is a skill published in the GitHub repository SteveVitali/agent-skills (12 stars, last pushed yesterday), licensed MIT. It adds 101 tokens to every session and 2,368 once invoked, about $0.0005 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-10.

Memory and contextProject managementagent-skillsai-agentsdeveloper-tools
Related

Other skills, from other repositories

neat-freak

Knowledge and governance closeout: reconcile project docs, rule files (CLAUDE.md/AGENTS.md), authorized agent memory, and workspace residue with what the code and runtime actually do, so the next session or the next person starts from one current answer. Trigger when the user names "neat-freak", "洁癖", or "/neat" — and…

KKKKhazix/khazix-skills · 202 tokens

state

Use when the user says 'update state', 'project state', 'where was I', or at session start to load current context.

cwinvestments/memstack · 29 tokens

handoff

Use when work is changing sessions, agents, or machines and the next pass needs a compact handoff document with current state, open questions, and next steps instead of raw chat history.

drvoss/everything-copilot-cli · 40 tokens

mastermind-project-history

Retrieve and reason from durable project decisions, failed approaches, audits, reports, and lessons without treating provenance, search rank, or user approval as technical proof. Use when asking why a design exists, whether an approach was tried, what supersedes an older decision, what prior evidence should constrain…

xcrft/mastermind · 79 tokens

project-context

Resume, handoff, and long-running repo work by keeping durable context across threads or agents: task briefs, logs, and reusable reference notes.

perhapsspy/project-legibility · 32 tokens

continue

Use when you need the Codex Copilot equivalent of Claude Copilot /continue: resume paused or previous work from tc tasks, work products, memory, and stream context.

Everyone-Needs-A-Copilot/claude-copilot · 37 tokens