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 skills add sunil-goyal-1502/project-memory --skill research-showgit 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/research-show)<a href="https://agentmods.dev/skills/sunil-goyal-1502/project-memory/research-show"><img src="https://agentmods.dev/badge/skills/sunil-goyal-1502/project-memory/research-show/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/skills/sunil-goyal-1502/project-memory/research-show"><img src="https://agentmods.dev/badge/skills/sunil-goyal-1502/project-memory/research-show.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.00007 | $0.00398 |
| Opus 5 | $0.00003 | $0.00199 |
| Sonnet 5 | $0.00001 | $0.00080 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
research-show 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 8d 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
Show Research Findings
Display research findings from .ai-memory/research.jsonl.
Steps
-
Read
.ai-memory/research.jsonl. If it doesn't exist or is empty, tell the user: "No research findings recorded yet. Use /project-memory:research-save to capture findings." -
Parse optional filter: If
$ARGUMENTSis provided, use it as a keyword filter — match against tags (exact), topic (substring, case-insensitive), and finding text (substring, case-insensitive). -
Display as a grouped table organized by primary tag (first tag in the tags array):
For each group:
## <Primary Tag> (<count>) | # | Topic | Finding | Confidence | Staleness | Date | |---|-------|---------|------------|-----------|------| | 1 | <topic> | <finding truncated to 80 chars> | <confidence> | <staleness> | <date> |If a filter was applied, show only matching entries.
-
Show summary:
- Total findings count (and filtered count if filter applied)
- Estimated token usage: count total characters across all
topic+finding+source_contextfields, divide by 4 - Staleness breakdown: how many stable / versioned / volatile
- If any entries have
supersedesset, note: "N entries have been superseded. Run /project-memory:research-compact to clean up." - Read cumulative stats from
.ai-memory/metadata.jsonstatsobject and display:"Cumulative memory savings: ~<totalTokens> tokens (~<totalCost>), ~<totalTime> saved across <totalHits> lookups"
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.
- 8d ago First seen · 35 lines · 7 tokens per session scan A 4d39ca406e5b
research-show 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 398 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.