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/owl-listener/designpowers/design-memorynpx skills add Owl-Listener/designpowers --skill design-memorygit clone --depth 1 https://github.com/Owl-Listener/designpowersWrote 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/owl-listener/designpowers/design-memory)<a href="https://agentmods.dev/skills/owl-listener/designpowers/design-memory"><img src="https://agentmods.dev/badge/skills/owl-listener/designpowers/design-memory.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.00091 | $0.02192 |
| Opus 5 | $0.00046 | $0.01096 |
| Sonnet 5 | $0.00018 | $0.00438 |
| Haiku 4.5 | $0.00009 | $0.00219 |
Grade A, and why
design-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 5d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Memory
Design memory is an observational record of how you design — the decisions you make, the styles you reach for, the habits and inclinations that show up across projects. It is a mirror, not a controller. It notices what you do and reflects it back to you out of curiosity. It does not steer future work.
The one rule that defines this skill
Design memory is descriptive, never prescriptive. It records what you did; it is not applied to drive new projects. The current project's direction comes from what you tell the team now (design-taste) and from any brand spec you provide (design-md / DESIGN.md) — never from this record. Observation that never feeds back into the work cannot mis-steer it, which is exactly why a record built across many different clients stays safe and honest: it's a journal, not a set of orders.
If you ever want to act on an observation, that's your call to make explicitly in the moment — the system will not quietly apply your past decisions to a new client's project.
Welcome Gate
BEFORE reading or updating design memory, check whether the Designpowers welcome sequence has been shown this session. If the user has not yet seen the welcome (the bird, the greeting, and the walkthrough offer), you MUST invoke the using-designpowers skill FIRST and complete the welcome sequence before returning here. The bird must appear before any work begins. No exceptions.
When to Use
- At project completion — observe the project's decisions and add them to the record
- When the user asks "how do I design?", "what are my habits?", "what's my style?" — produce the report
- When the user makes a notably characteristic choice — note it as an observation
- It is not loaded to constrain a new project. (Loading at project start is only to show the user their report if they want it, not to feed preferences into the pipeline.)
The Record (taste-profile.md)
Lives at ~/.designpowers/taste-profile.md (cross-project). It is a journal of observations about how the user works — not a rulebook. Every entry is phrased as something observed, with evidence, never as an instruction for future work.
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.
- 5d ago First seen · 162 lines · 91 tokens per session scan A d09bcc4ee549
design-memory is a skill published in the GitHub repository Owl-Listener/designpowers (240 stars, last pushed 2mo ago), licensed MIT. It adds 91 tokens to every session and 2,192 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-08-30.
Other skills, from other repositories
semantix
Install and use the semantix memory kernel as a middleware in your agent: extract user preferences / workflows / experience from past sessions, retrieve and inject them on demand. One binary + your agent's own tools.
distill-session-knowledge
Offline-mine this project's pi session JSONL logs into reusable, verified knowledge: extracts faults, decisions, corrections, procedures and docs, promotes only recurring patterns, and routes artifacts into skillmanage, memory and docs. Use on "mine my sessions", "distill session knowledge", "extract lessons from…
remember
Save durable facts to nui persistent memory (/.nui/memory/) when the user asks.
list-learned-actions
Explicit Codex workflow: List persisted reusable actions, UI skeletons, and legacy feedback memories before composing device primitives.
session-memory
Mandatory memory persistence system across session resets using three markdown surfaces in .claude/cc10x/. Iron law - every workflow must load at start and update at end.
knowledge-curation
Context priming before work (bd prime) and self-reflection after completion to extract patterns, gotchas, and decisions into the knowledge base.