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 instructions/bbonin023/workspace-memory/agents-mdgit clone --depth 1 https://github.com/bbonin023/workspace-memoryWrote 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/instructions/bbonin023/workspace-memory/agents-md)<a href="https://agentmods.dev/instructions/bbonin023/workspace-memory/agents-md"><img src="https://agentmods.dev/badge/instructions/bbonin023/workspace-memory/agents-md.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 | $0.01832 | $0.01832 |
| Opus 5 | $0.00916 | $0.00916 |
| Sonnet 5 | $0.00366 | $0.00366 |
| Haiku 4.5 | $0.00183 | $0.00183 |
Grade A, and why
workspace-memory AGENTS.md 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 3d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — orientation for AI agents
If you are a human, you probably want
README.mdinstead. This file is written for AI agents (Claude, GPT, Gemini, local models, etc.) who have been pointed at this repository and asked to help a human adopt or use the workspace-memory convention.
What this repository is
A documentation convention. Five markdown files per active project, plus a master orientation file at the workspace root, plus a reduced-form archive for completed projects. No code, no installer, no dependencies. The convention is described in detail in conventions.md; the templates to copy are in skeletons/; worked examples are in examples/.
The convention exists so that any project's current state, architecture, runbook, and decision history live in predictable locations with predictable names. This makes the project navigable to humans who haven't seen it in months and to AI agents who have never seen it at all.
What the human is likely asking you to do
One of three things, in roughly decreasing order of frequency:
1. Set up the convention in their workspace for the first time. They have an existing directory of projects (or are starting fresh) and want to adopt this layout. Your job is to scaffold the master AGENTS.md at their workspace root, create projects/active/ and projects/archive/ directories, and walk them through populating the first project. Do not try to populate every project at once — pick one with the human and do it well, then let them apply the pattern to the rest.
2. Add a new project to a workspace that already uses the convention. A master AGENTS.md already exists. Your job is to create projects/active/<slug>/ with the five-file skeleton, fill in what you can from the conversation, and update the project table in the master file. Confirm the slug with the human before creating directories — slugs are kebab-case, 2–50 chars, must start with a letter.
3. Migrate an existing project's docs into the convention. The human has scattered notes, READMEs, or partial docs and wants them organized into the five-file structure. Your job is to read what they have, sort it into the right files, and flag what's missing. Do not invent content to fill out sections you have no information for — leave TODO markers and tell the human what you'd need to know.
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.
- 3d ago First seen · 92 lines · 1,832 tokens per session scan A e79382a929da
workspace-memory AGENTS.md is an instructions file published in the GitHub repository bbonin023/workspace-memory (2 stars, last pushed 3mo ago), licensed MIT. It adds 1,832 tokens to every session, about $0.0092 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-08-31.
Other instructions, from other repositories
hindsight CLAUDE.md
Claude Code instructions for vectorize-io/hindsight, covering claude.md, project overview, development commands, local development (api + ui) and start both api server and control plane ui.
honcho CLAUDE.md
Claude Code instructions for plastic-labs/honcho, covering claude.md, honcho overview, what is honcho?, core concepts and peer paradigm.
Dragon-Brain CLAUDE.md
Instructions for iikarus/Dragon-Brain, covering dragon brain — claude.md, the harness, audit remediation (april–may 2026, complete 2026-05-09), the lie this audit closed and the contract that matters now.
brainlayer AGENTS.md
Instructions for EtanHey/brainlayer, covering brainlayer — a letter from etan, brainlayer agent notes (operational), review guidelines, key paths and database.
mnemonic memory-files.instructions.md
Instructions for modeled-information-format/mnemonic, covering memory file guidelines (mif level 3), required frontmatter fields, optional temporal fields, optional provenance fields and memory types.
dakera-cli CLAUDE.md
Instructions for Dakera-AI/dakera-cli, covering dakera-cli, key commands, architecture and conventions.