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 instructions/ozgurkarahan/ai-agent-memory/plan-weekgit clone --depth 1 https://github.com/ozgurkarahan/ai-agent-memoryWrote 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/instructions/ozgurkarahan/ai-agent-memory/plan-week)<a href="https://agentmods.dev/instructions/ozgurkarahan/ai-agent-memory/plan-week"><img src="https://agentmods.dev/badge/instructions/ozgurkarahan/ai-agent-memory/plan-week.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.00320 | $0.00320 |
| Opus 5 | $0.00160 | $0.00160 |
| Sonnet 5 | $0.00064 | $0.00064 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
ai-agent-memory plan-week.instructions.md 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
Plan Week
When the user says "plan week", "Monday plan", or "/plan-week":
Resolve the memory root
Resolve WIKI_ROOT using memory/schema.md, then schema.md, then the pointer in AGENT.md. Stop with the missing path if none contains both schema.md and index.md. All paths below are relative to WIKI_ROOT.
- Resolve active ISO week (TZ Europe/Paris) →
ops/weekly/2026-W{NN}.md. If missing, create the minimal weekly skeleton defined by theingestskill. - Lift carry-over from prior week's
### Seed for W{NN}block. - Find open
- [ ]todos recursively underwiki/, prioritizing pages updated in the last 14 days. - Optionally use any connected work-data source available to the agent for the next 7 days of calendar, flagged mail, or open collaboration threads. Skip this step when no such tool is available.
- Draft
## 🎯 Monday plangrouped by### [[topic]]. Show diff. User confirms. - Update
touches: []frontmatter with topic slugs touched. Bumpdate_updated.
Anti-patterns:
- ❌ Do not write to
ops/activity.jsonl— planning ≠ work. - ❌ Do not auto-resolve todos.
- ❌ Topics must be slugs in
index.md— else group under### unmapped.
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 · 24 lines · 320 tokens per session scan A 960ea6df4e15
ai-agent-memory plan-week.instructions.md is an instructions file published in the GitHub repository ozgurkarahan/ai-agent-memory (8 stars, last pushed 1mo ago), licensed MIT. It adds 320 tokens to every session, about $0.0016 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 instructions, from other repositories
vespertide AGENTS.md
AGENTS.md instructions for dev-five-git/vespertide, covering vespertide knowledge base, structure, where to look, data flow and conventions.
aeon CLAUDE.md
Instructions for aeonfun/aeon, covering aeon, how aeon works, strategy, voice and soul file hierarchy (read in this order).
wayland-core copilot-instructions.md
Copilot instructions for FerroxLabs/wayland-core, covering ijfw rules, output discipline, memory routing, context discipline and cross-audit.
mcp-structured-memory CLAUDE.md
Claude Code instructions for nmeierpolys/mcp-structured-memory, a project described as: Structured Memory MCP Server.
inkwell-memory CLAUDE.md
Instructions for veronchenko/inkwell-memory, covering claude.md — inkwellmemory, layout, multi-tenant mode (inkwellmultitenant=1), conventions and testing.
RNR-Enhanced-Cognee AGENTS.md
AGENTS.md instructions for vincentspereira/RNR-Enhanced-Cognee, covering rnr enhanced cognee implementation for codex, critical requirements, 1. ascii-only output (no unicode encoding), 2. dynamic categories (no hardcoded categories) and 3. standard memory mcp interface.