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 SII-Holos/synergy --skill inspect-sessionsgit clone --depth 1 https://github.com/SII-Holos/synergyWrote 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/sii-holos/synergy/inspect-sessions)<a href="https://agentmods.dev/skills/sii-holos/synergy/inspect-sessions"><img src="https://agentmods.dev/badge/skills/sii-holos/synergy/inspect-sessions/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/sii-holos/synergy/inspect-sessions"><img src="https://agentmods.dev/badge/skills/sii-holos/synergy/inspect-sessions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00060 | $0.00678 |
| Opus 5 | $0.00030 | $0.00339 |
| Sonnet 5 | $0.00012 | $0.00136 |
| Haiku 4.5 | $0.00006 | $0.00068 |
Grade A, and why
inspect-sessions 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 yesterday.
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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inspect Session State
Start with Recovery-safe Commands
Preserve the target SYNERGY_HOME and working directory so Scope resolution matches the session.
synergy session list --format json --max-count 20
synergy session list --with-health --format json
synergy session inspect <session-id> --json
session inspect reads health metadata without hydrating the message history. Supply --scope <scope-id> only when the global session index is missing.
For index problems, preview repairs before any mutation:
synergy session repair --dry-run --json
Run --apply or session delete --yes only when the user explicitly requests the state change and the inspection proves it is appropriate.
Inspect Raw Storage Read-only
Read Storage and paths and Sessions and messages before interpreting records.
Resolve the root as <SYNERGY_HOME or OS home>/.synergy/data/. Use the session index to find the owning Scope, then inspect:
session_index/<session-id>.json
sessions/<scope-id>/<session-id>/info.json
sessions/<scope-id>/<session-id>/messages/<message-id>/info.json
sessions/<scope-id>/<session-id>/messages/<message-id>/parts/<part-id>.json
Use jq, rg, find, and ls only for read-only inspection. Derive exact paths from packages/harness/src/storage/path.ts when a collection name is uncertain; do not rely on an old directory diagram.
Reconstruct the Invariants
Check independently:
- session info readability, Scope, parent/child lineage, workflow, and
pendingReply - root user message and assistant
rootID/parentIDsemantics visible,includeInContext, messageorigin, and partorigin- tool-call/result pairing and terminal assistant state
- inbox
mode(task,steer, orcontext) - compaction anchor and continuation summary
- session indexes versus readable on-disk records
- migration log entries for the owning domain
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.
- yesterday Changed a55e9d7e43fd
- 10d ago First seen · 67 lines · 60 tokens per session scan A e8bbc1e47ac8
inspect-sessions is a skill published in the GitHub repository SII-Holos/synergy (490 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 678 once invoked, about $0.0003 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.