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/soulcodex/agentic/plan-memory-indexnpx skills add soulcodex/agentic --skill plan-memory-indexgit clone --depth 1 https://github.com/soulcodex/agenticWhat 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.00040 | $0.01069 |
| Opus 5 | $0.00020 | $0.00535 |
| Sonnet 5 | $0.00008 | $0.00214 |
| Haiku 4.5 | $0.00004 | $0.00107 |
Grade A, and why
plan-memory-index 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Memory Index Skill
Keep a compact, queryable memory of plans that were already applied, so agents can recover only the right context first and fetch full external issue details later.
Use this skill for concise continuity memory. Do not use it as a full session log.
Step 1 - Ensure Deterministic Storage Layout
Ensure this directory structure exists:
.agentic/
memories/
plan-memory/
index.md
entries/
plans/
INDEX.md
Rules:
- Create
.agentic/memories/plan-memory/and.agentic/memories/plan-memory/entries/when missing. - Keep the memory index filename exactly
.agentic/memories/plan-memory/index.md. - Treat
.agentic/plans/INDEX.mdas the canonical plans index (do not create.agentic/plans/index.md).
Step 2 - Create or Update a Memory Entry
Create one Markdown file per memory entry:
.agentic/memories/plan-memory/entries/YYYY-MM-DD-{plan-slug}.md
Example:
.agentic/memories/plan-memory/entries/2026-05-16-issue-149-plan-memory-index.md
Frontmatter fields:
id: stable unique ID, e.g.plan-memory-2026-05-16-001plan_slug: kebab-case plan identifiersummary: concise applied-plan excerptlinked_issues: optional list of GitHub issue URLsplan_file: optional path to canonical plan file under.agentic/plans/status: one ofdraft,in-progress,done,supersededlast_used_at: ISO-8601 UTC timestamptags: short list for retrieval
Use memory-entry-template.md.
Step 3 - Enforce Summary Length Guidance
Keep memory entries high signal and small:
summary: target 1 to 3 sentences.- Hard cap: 280 characters.
- Do not copy full issue bodies, long logs, or full plans into memory entries.
- If more detail is needed, store a short pointer in
summaryand defer deep fetch.
Step 4 - Upsert .agentic/memories/plan-memory/index.md
Create .agentic/memories/plan-memory/index.md from index-template.md if missing.
Then add or update a single row for the memory entry.
What ships with it
2 files 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.
- 2d ago First seen · 135 lines · 40 tokens per session scan A 089115a9756d
plan-memory-index is a skill published in the GitHub repository soulcodex/agentic (10 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 1,069 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
survey-design
Design unbiased survey instruments — question wording, scales, and sampling — to measure attitudes at scale. Use when you need quantitative breadth. For behavioural experiments, use a-b-test-design (prototyping-testing).
design-negotiation
Advocate for design quality, scope, and timeline with partners and leadership using evidence and shared goals. Use in the conversation itself. For the commercial vocabulary behind it, use business-design (ux-strategy).
design-debt-audit
Inventory and prioritise accumulated design inconsistencies across a product. Use when drift has built up over time. For token coverage specifically use design-token-audit (designer-toolkit); for WCAG gaps use accessibility-audit (design-systems).
design-impact-reporting
Communicate design's contribution to business and user outcomes in stakeholder language. Use when reporting results upward. For choosing the metrics in the first place, use metrics-definition (ux-strategy).
research-repository
Build a repository that makes findings findable, reusable, and cumulative across teams. Use when the same research keeps getting redone. For synthesising one study, use affinity-diagram.
design-system-governance
Define how the system evolves — contribution model, versioning, deprecation, and change management. Use when multiple teams contribute. For driving uptake use design-system-adoption (designer-toolkit); for design file history use version-control-strategy (design-ops).