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 LameGz/synapse-graph-skills --skill synapse-timelinegit clone --depth 1 https://github.com/LameGz/synapse-graph-skillsWrote 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/lamegz/synapse-graph-skills/synapse-timeline)<a href="https://agentmods.dev/skills/lamegz/synapse-graph-skills/synapse-timeline"><img src="https://agentmods.dev/badge/skills/lamegz/synapse-graph-skills/synapse-timeline/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/lamegz/synapse-graph-skills/synapse-timeline"><img src="https://agentmods.dev/badge/skills/lamegz/synapse-graph-skills/synapse-timeline.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.00093 | $0.01012 |
| Opus 5 | $0.00046 | $0.00506 |
| Sonnet 5 | $0.00019 | $0.00202 |
| Haiku 4.5 | $0.00009 | $0.00101 |
Grade A, and why
synapse-timeline 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 10d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Synapse Timeline
v1.5 product shape: this skill remains a read-only timeline and issue query entry. For full project context restoration, prefer the core Project Resume flow (project_resume.py --project <path>) before loading individual nodes.
Overview
Read-only query tool that parses meta/*.md node files and MEMORY_MAP.json to answer time-based and progress questions. Never modifies files. Never writes.
Two query modes:
- Timeline (default): Reads
## Change Logsections, sorted newest-first - Issues (
--issues): Reads## Open Issuessections, sorted by node path
Trigger Patterns (MANDATORY)
| User says... | Action |
|---|---|
| "最近改了啥" / "最近两天改了什么" / "这周做了什么" | query_timeline.sh --recent N --summary |
| "上次 XX 是什么时候" / "when did we last touch X" | query_timeline.sh --node meta/XX.md |
| "有哪些 open issues" / "还没解决的问题" / "还有啥没做" | query_timeline.sh --issues |
| "进度怎么样了" / "项目状态" / "做到什么程度了" | query_timeline.sh --issues --summary |
| "XX 模块最近的变化" / "timeline for auth" | query_timeline.sh --tag XX --recent 7 --summary |
| "从 YYYY-MM-DD 之后的改动" | query_timeline.sh --since YYYY-MM-DD |
If the user asks about progress but the project has MEMORY_MAP.md, prefer reading ## Progress Summary from the MAP directly (cheaper). Use query_timeline.sh when the user wants dated, detailed entries.
Quick Start
# From skill directory
bash scripts/query_timeline.sh --project <project-path> [filters]
# Or from anywhere
bash <path-to-skill>/scripts/query_timeline.sh --project <project-path> [filters]
Filter Reference
| Flag | Argument | Effect |
|---|---|---|
--project |
<path> |
Root of the Synapse project (must contain meta/) |
--node |
meta/feat_login.md |
Show entries for one specific node only |
--tag |
auth / 支付 |
Filter nodes matching tag or alias (uses MEMORY_MAP.json for lookup, falls back to frontmatter parsing) |
--since |
YYYY-MM-DD |
Only entries on or after this date |
--recent |
N (days) |
Only entries from last N days (overrides --since) |
--limit |
N |
Max entries shown (default: 20) |
--summary |
(flag) | Print grouped counts before entries |
--issues |
(flag) | Show Open Issues instead of Change Log entries |
-h / --help |
(flag) | Print usage |
What ships with it
3 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.
- 10d ago First seen · 99 lines · 93 tokens per session scan A fbf4121743bc
synapse-timeline is a skill published in the GitHub repository LameGz/synapse-graph-skills (11 stars, last pushed 3mo ago), licensed MIT. It adds 93 tokens to every session and 1,012 once invoked, about $0.0005 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-30.
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…
shellm
Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.