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/686f6c61/alfred-dev/memorynpx skills add 686f6c61/alfred-dev --skill memorygit clone --depth 1 https://github.com/686f6c61/alfred-devWhat 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.00053 | $0.00605 |
| Opus 5 | $0.00026 | $0.00302 |
| Sonnet 5 | $0.00011 | $0.00121 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
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.
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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memoria persistente de Alfred
Registrar y consultar decisiones del proyecto a través del servidor MCP alfred-memory. No inventar historial. Si la herramienta no está disponible, decirlo y no simular resultados.
Nombres reales de las tools
Claude Code expone las tools del plugin con prefijo MCP. Usar estos nombres, no los cortos:
mcp__plugin_alfred-dev_alfred-memory__memory_searchmcp__plugin_alfred-dev_alfred-memory__memory_get_decisionsmcp__plugin_alfred-dev_alfred-memory__memory_get_iterationmcp__plugin_alfred-dev_alfred-memory__memory_get_timelinemcp__plugin_alfred-dev_alfred-memory__memory_statsmcp__plugin_alfred-dev_alfred-memory__memory_log_decisionmcp__plugin_alfred-dev_alfred-memory__memory_update_decisionmcp__plugin_alfred-dev_alfred-memory__memory_link_decisionsmcp__plugin_alfred-dev_alfred-memory__memory_health
Si el runtime muestra un prefijo distinto, usar el que aparezca en la lista de tools, siempre del servidor alfred-memory.
Qué se escribe y qué no
Sí: decisiones de diseño, resultado de gates, handoffs, UAT y commits hechos en una sesión de Alfred.
No: historial antiguo de Git, cada Read/Glob/Grep, consejos operativos ni kanban vacío.
Llamar a memory_log_decision solo cuando haya una elección real de diseño, seguridad o entrega. No registrar cada edit. Si la decisión es de arquitectura o compliance, el Markdown vivo (docs/adr/, docs/project/compliance.md) es lo que lee un humano; la memoria no lo sustituye.
Campos mínimos: título, contexto, alternativas descartadas, justificación, etiquetas.
Consulta
Para "por qué decidimos X" o "qué hicimos la última vez": memory_search o memory_get_decisions con el término y, si aplica, rango o tags.
Si no hay filas, responder que no hay registros. No inferir.
No existe el agente librarian. Esta skill y /alfred-dev:memory-ui son la vía de consulta histórica.
UI
La vista gráfica es /alfred-dev:memory-ui. Esta skill no arranca el servidor HTTP. Para cerrarla: /alfred-dev:memory-ui stop. Al terminar la sesión de Claude se detiene sola.
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.
- 2d ago First seen · 47 lines · 53 tokens per session scan A ba29034f4254
memory is a skill published in the GitHub repository 686f6c61/alfred-dev (119 stars, last pushed 18d ago), licensed MIT. It adds 53 tokens to every session and 605 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.