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 strigov/superpowers-strigov-ver --skill architecture-memorygit clone --depth 1 https://github.com/strigov/superpowers-strigov-verWrote 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/strigov/superpowers-strigov-ver/architecture-memory)<a href="https://agentmods.dev/skills/strigov/superpowers-strigov-ver/architecture-memory"><img src="https://agentmods.dev/badge/skills/strigov/superpowers-strigov-ver/architecture-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/strigov/superpowers-strigov-ver/architecture-memory"><img src="https://agentmods.dev/badge/skills/strigov/superpowers-strigov-ver/architecture-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.00086 | $0.01184 |
| Opus 5 | $0.00043 | $0.00592 |
| Sonnet 5 | $0.00017 | $0.00237 |
| Haiku 4.5 | $0.00009 | $0.00118 |
Grade A, and why
architecture-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 9d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Memory (ARCHI.md)
docs/ARCHI.md is a curated, always-current snapshot of the repository's architecture — the agent's long-term memory of the codebase. Concept borrowed from TRIP-workflow (MIT).
Why: without it, every session re-derives the architecture through glob/grep/read passes — slow, token-hungry, and prone to guessing ("there's probably a utils folder…"). With it, one read gives the full picture. Unlike CLAUDE.md, ARCHI.md is purely about architecture and tool-agnostic — any agent (Claude, Codex, other) can consume it; reference it from CLAUDE.md if you want it in every conversation.
It is optional infrastructure: nothing in this plugin requires it. But when it exists, the dev-orchestrator prompts already exploit it — the Opus plan writer and the implementers read it first, and Explore passes start from it instead of from zero.
What goes in (and what doesn't)
Keep: what exists and why it is shaped that way. Remove: how (implementation specifics that belong in the code).
Recommended H2 skeleton — adapt to the project:
## Overview— what the system is, 3–5 sentences.## Stack— languages, frameworks, key deps, versions that matter.## Module map— directories/modules with one-line responsibilities. Summarize file groups (src/auth/ — auth UI components (Login, Logout, Register)), never exhaustive file listings.## Data flow / control flow— how a request/event travels. A mermaid diagram beats prose.## Contracts— public API surface, event/schema shapes, invariants other modules rely on.## Conventions— error handling, logging, naming, test layout; the things reviewers enforce.## Decisions— short ADR-style log: choice, why, date. Append-only.
Density rules (these keep the file useful):
- Tables and bullet fragments over paragraphs;
codefor every path/command/type. - One concept explained once — cross-reference, don't repeat.
- No implementation walk-throughs:
useTranscription: orchestrates transcription fetching and state— nothing about its useState internals.
What ships with it
1 file 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.
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.
- 9d ago First seen · 73 lines · 86 tokens per session scan A e39009ead1a5
architecture-memory is a skill published in the GitHub repository strigov/superpowers-strigov-ver (4 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 1,184 once invoked, about $0.0004 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 skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.