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.
git clone --depth 1 https://github.com/javiarmesto/ALDC-AL-Development-CollectionWrote 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/commands/javiarmesto/aldc-al-development-collection/al-memory-create)<a href="https://agentmods.dev/commands/javiarmesto/aldc-al-development-collection/al-memory-create"><img src="https://agentmods.dev/badge/commands/javiarmesto/aldc-al-development-collection/al-memory-create/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/commands/javiarmesto/aldc-al-development-collection/al-memory-create"><img src="https://agentmods.dev/badge/commands/javiarmesto/aldc-al-development-collection/al-memory-create.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.00040 | $0.02832 |
| Opus 5 | $0.00020 | $0.01416 |
| Sonnet 5 | $0.00008 | $0.00566 |
| Haiku 4.5 | $0.00004 | $0.00283 |
Grade A, and why
al-memory-create 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 — 533 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AL Memory File Generator
Generate and maintain a memory.md file that serves as the project memory - tracking decisions, changes, learnings, and important conversations across development sessions.
Purpose
The memory.md file provides:
- Session Continuity: What happened in previous sessions
- Decision Log: Why things were done a certain way
- Problem/Solution Patterns: What issues occurred and how they were solved
- TODO Tracking: What needs to be done next
- Learning Journal: Insights gained during development
- Context for AI: Prevents re-asking questions or repeating mistakes
This enables AI assistants and developers to pick up where they left off and build on previous work.
Execution Steps
1. Initialize Memory Structure
If memory.md doesn't exist, create with this template:
# Project Memory - [Extension Name]
> **Purpose**: Continuous memory across development sessions
> **Maintained by**: AI assistants and developers
> **Last Updated**: [Date]
## Quick Reference
**Current Focus**: [What we're working on now]
**Next Steps**: [ImMEDIUMte next actions]
**Blockers**: [Current blockers if any]
---
---
## Session Log
### [Date] - Session [N]
**Focus**: [What was worked on]
**Completed**:
- [Task 1]
- [Task 2]
**Decisions Made**:
- **[Decision]**: [Rationale]
**Problems Encountered**:
- **[Problem]**: [Solution or workaround]
**Next Session**:
- [ ] [Task to continue]
- [ ] [Task to start]
**Notes**:
- [Any important observations]
---
---
## Decision Log
### [Date] - [Decision Title]
**Context**: [Why this decision needed to be made]
**Options Considered**:
1. [Option 1]: [Pros/Cons]
2. [Option 2]: [Pros/Cons]
**Decision**: [What was chosen]
**Rationale**: [Why this option]
**Impact**: [What this affects]
**Review Date**: [When to revisit if applicable]
---
---
## Problem/Solution Patterns
### [Problem Category] - [Specific Issue]
**Symptom**: [What we observed]
**Root Cause**: [What was actually wrong]
**Solution**: [How we fixed it]
**Prevention**: [How to avoid in future]
**Related Code**: [File paths or line numbers]
---
---
## Learning Journal
### [Date] - [Topic/Insight]
**What We Learned**: [Key insight or pattern discovered]
**Why It Matters**: [Impact on project]
**Where Applied**: [Code locations]
**Resources**: [Links to docs, articles that helped]
---
---
## Code Evolution
### [Feature/Module Name]
**v1.0** - [Date]
- Initial implementation
- [Key characteristics]
**v1.1** - [Date]
- Changed: [What changed]
- Reason: [Why it changed]
- Migration: [How to adapt if needed]
---
---
## TODO & Backlog
### High Priority
- [ ] [Task] - [Why important] - [Target date]
### Medium Priority
- [ ] [Task] - [Context]
### Future Ideas
- [ ] [Idea] - [Rationale]
### Done ✅
- [x] [Completed task] - [Date completed]
---
---
## Questions & Answers
### [Question]
**Asked**: [Date]
**Answer**: [The answer found]
**Source**: [Where answer came from - docs, testing, expert]
---
---
## Integration Points
### [External System/Extension Name]
**First Integrated**: [Date]
**Current Status**: [Active/Deprecated/Planned]
**Contact Point**: [Method - API/Event/etc]
**Issues Encountered**: [Problems and solutions]
**Dependencies**: [What depends on this]
---
---
## Performance Tracking
### [Feature/Operation]
**Baseline**: [Initial performance metrics]
**Optimizations Applied**:
- [Date]: [Change] → [Result]
**Current State**: [Latest metrics]
**Target**: [Performance goal]
---
---
## Testing Insights
### [Test Scenario]
**First Tested**: [Date]
**Results**: [What we found]
**Edge Cases Discovered**:
- [Edge case 1]: [How handled]
**Regression History**: [If this broke before, when and why]
---
---
## Communication Log
### [Date] - [Stakeholder/Team Member]
**Topic**: [What was discussed]
**Decisions**: [Agreements reached]
**Action Items**: [Who does what]
**Follow-up**: [When to check back]
---
---
## Environment Notes
### Development Setup
**Last Working Config**: [Date]
- BC Version: [Version]
- Extensions: [Key extensions used]
- Settings: [Important VS Code/AL settings]
**Known Issues**:
- [Issue]: [Workaround]
---
---
## Deprecated Patterns
### [Pattern Name]
**Used**: [Date range when this was used]
**Replaced By**: [New pattern]
**Migration Guide**: [How to update old code]
**Reason for Deprecation**: [Why we stopped using it]
---
---
## Useful Snippets
### [Snippet Name]
```al
[Code snippet that proved useful]
Use Case: [When to use this]
Source: [Where this came from]
Meeting Notes
[Date] - [Meeting Type]
Attendees: [Who was there]
Topics: [What was discussed]
Decisions: [What was decided]
Actions: [Who does what by when]
Maintenance Log
[Date] - [Maintenance Activity]
What: [What was maintained]
Why: [Reason for maintenance]
Changes: [What changed]
Impact: [What this affects]
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 · 533 lines · 40 tokens per session scan A dfbaea34309b
al-memory-create is a command published in the GitHub repository javiarmesto/ALDC-AL-Development-Collection (103 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 2,832 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-30.
Other commands, from other repositories
ingest
Ingest source material into an active wiki. Accepts URLs, file paths, PDFs, freeform text, or processes the inbox. Supports tweets via Grok MCP.
session
Capture, list, rehydrate, and promote llm-wiki session context. Supports automated hook capture into HUB/.sessions plus explicit promotion into topic raw notes.
memory-search
Command "memory-search" from smith-horn/skillsmith, covering memory-search, usage, options, examples and search memory (v3 default search type is semantic).
ship
Run the Android pre-launch checklist via parallel fan-out to specialist personas, then synthesize a go/no-go decision with rollback and staged rollout plan.
code-simplify
Simplify code incrementally while preserving behavior exactly.
save-from-chat
Scan this chat session and save important learnings to the knowledge base.