Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add sunil-goyal-1502/project-memory/plugin install 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/research-save)<a href="https://agentmods.dev/skills/sunil-goyal-1502/project-memory/research-save"><img src="https://agentmods.dev/badge/skills/sunil-goyal-1502/project-memory/research-save.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.1 | $0.00007 | $0.00656 |
| Opus 5 | $0.00003 | $0.00328 |
| Sonnet 5 | $0.00001 | $0.00131 |
| Haiku 4.5 | $0.00001 | $0.00066 |
Grade A, and why
research-save 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 7d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Save Research Finding
Save a research finding to .ai-memory/research.jsonl.
Steps
-
Parse the input:
$ARGUMENTScontains the finding text. If empty, ask the user what finding they want to save. -
Auto-extract metadata from the finding text:
- topic: Extract a 5-15 word noun phrase summarizing the finding. Should be scannable and include library/tool names if relevant.
- tags: Extract 1-5 keywords (lowercase). Include library names, concepts, and key technical terms.
- staleness: Classify as:
"stable"— language behavior, protocol specs, math properties (won't change)"versioned"— library/framework-specific behavior (setversion_anchoredif a version is mentioned)"volatile"— external service behavior, API responses, rate limits (may change anytime)
- confidence: Default to
0.9for explicit user-provided findings.
-
Check for overlapping entries: Read
.ai-memory/research.jsonland look for entries with:- 2+ matching tags AND similar topic (substring match)
- If found, show the existing entry and ask: "Existing finding found on this topic. Supersede it? (y/n)"
- If superseding, set
"supersedes": "<existing-id>"in the new entry.
-
Generate the entry:
{ "id": "<8-char-random-hex>", "ts": "<ISO8601-timestamp>", "topic": "<extracted topic>", "tags": ["<extracted tags>"], "finding": "<the finding text from $ARGUMENTS>", "source_tool": "claude-code", "source_context": "Explicitly saved by user", "confidence": 0.9, "staleness": "<classified>", "supersedes": null, "version_anchored": null } -
Append the JSON line to
.ai-memory/research.jsonl. -
Run sync to update tool-specific files:
node -e "require('${CLAUDE_PLUGIN_ROOT}/scripts/sync-tools.js').syncAll(process.cwd())" -
Report: Show the saved finding with its topic, tags, and staleness classification.
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.
- 7d ago First seen · 61 lines · 7 tokens per session scan A 361365da0943
research-save is a skill published in the GitHub repository sunil-goyal-1502/project-memory (8 stars, last pushed 4mo ago), licensed MIT. It adds 7 tokens to every session and 656 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.