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/sunil-goyal-1502/project-memory/memory-initnpx skills add sunil-goyal-1502/project-memory --skill memory-initgit clone --depth 1 https://github.com/sunil-goyal-1502/project-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/skills/sunil-goyal-1502/project-memory/memory-init)<a href="https://agentmods.dev/skills/sunil-goyal-1502/project-memory/memory-init"><img src="https://agentmods.dev/badge/skills/sunil-goyal-1502/project-memory/memory-init.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.00008 | $0.00428 |
| Opus 5 | $0.00004 | $0.00214 |
| Sonnet 5 | $0.00002 | $0.00086 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
memory-init 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 3d 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
Initialize Project Memory
Set up the .ai-memory/ directory in the current project root for cross-tool decision tracking.
Steps
-
Create the
.ai-memory/directory in the project root (current working directory). -
Create these files:
.ai-memory/decisions.jsonl— empty file (canonical decision store).ai-memory/research.jsonl— empty file (canonical research store).ai-memory/metadata.json— with this content:{ "tokenCount": 0, "lastSync": null, "sessionCount": 0, "decisionCount": 0, "researchCount": 0, "researchTokenCount": 0 }.ai-memory/.gitignore— with this content:# Transcript data is ephemeral and potentially sensitive .last-session.txt
-
Run the sync script to generate tool-specific instruction files: Run via Bash:
node -e "require('${CLAUDE_PLUGIN_ROOT}/scripts/sync-tools.js').syncAll(process.cwd())"This will create:
.github/copilot-instructions.md(with self-referential save instructions for Copilot).cursor/rules/project-decisions.mdc(with frontmatter + save instructions for Cursor)CLAUDE.md(with project decisions section between markers, or update existing)
-
Report success with a summary:
- List all created files
- Suggest: "Add
.ai-memory/to git to share decisions across the team" - Suggest: "Use
/project-memory:memory-saveto record your first decision" - Note: "Copilot and Cursor instruction files include self-referential save instructions — those tools can now save decisions directly to the canonical store"
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.
- 3d ago First seen · 48 lines · 8 tokens per session scan A 013f564f105c
memory-init is a skill published in the GitHub repository sunil-goyal-1502/project-memory (8 stars, last pushed 4mo ago), licensed MIT. It adds 8 tokens to every session and 428 once invoked, about $0.0000 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
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.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…