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/lwtlong/aida/aida-remembernpx skills add LWTlong/aida --skill aida-remembergit clone --depth 1 https://github.com/LWTlong/aidaWrote 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/lwtlong/aida/aida-remember)<a href="https://agentmods.dev/skills/lwtlong/aida/aida-remember"><img src="https://agentmods.dev/badge/skills/lwtlong/aida/aida-remember.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.00039 | $0.00388 |
| Opus 5 | $0.00019 | $0.00194 |
| Sonnet 5 | $0.00008 | $0.00078 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
aida-remember 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 4d 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.
What it actually says
AIDA Remember
Goal
Persist one project decision as a MADR-format file in .claude/rules/decisions/ so future Claude sessions can load it automatically via paths frontmatter.
Steps
-
Understand the decision — Ask the user (or infer from context):
- Title: short phrase naming the decision, e.g. "Use optimistic locking for cart updates"
- Context: why was this decision needed? What problem, constraints, alternatives were considered?
- Decision: what was decided and why?
- Consequences (optional): trade-offs, things that changed
- Paths (optional): file globs this decision applies to, e.g.
["src/cart/**", "src/orders/**"]
-
Call
aida_rememberwith the structured data. -
Confirm to the user:
✓ Decision saved:
<title>File:.claude/rules/decisions/<slug>.mdPaths scope:<paths or "global">This decision will be auto-loaded by Claude Code when you edit files matching the paths pattern.
Tips for Good Decisions
- Title: "Use X for Y" or "Don't use X because Y" — active voice, specific
- Context: include what you tried, what failed, what constraints forced the choice
- Paths: if the decision only applies to one module, scope it — this prevents context bloat in unrelated sessions
- Consequences: be honest about trade-offs — future developers need to know the ceiling, not just the choice
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.
- 4d ago First seen · 35 lines · 39 tokens per session scan A 9e8c173292c3
aida-remember is a skill published in the GitHub repository LWTlong/aida (8 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 388 once invoked, about $0.0002 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
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…
auditing-subgroup-fairness
Audit an OpenMed NER or de-identification model for performance disparities across demographic subgroups (sex, age band, race/ethnicity when available) using openmed.eval.fairnessreport. Use when the user wants per-subgroup recall and leakage, wants to check whether de-identification under-protects a group, wants to…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
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…