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 commands/kitepon/throughline/sc-detailgit clone --depth 1 https://github.com/kitepon/ThroughlineWrote 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/commands/kitepon/throughline/sc-detail)<a href="https://agentmods.dev/commands/kitepon/throughline/sc-detail"><img src="https://agentmods.dev/badge/commands/kitepon/throughline/sc-detail.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.00031 | $0.00241 |
| Opus 5 | $0.00015 | $0.00120 |
| Sonnet 5 | $0.00006 | $0.00048 |
| Haiku 4.5 | $0.00003 | $0.00024 |
Grade A, and why
sc-detail 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
以下の Bash コマンドを実行し、結果を全文そのまま表示してください（要約せず、一字一句）。
throughline detail "$ARGUMENTS"
使い方
/sc-detail 14:23:05— 指定時刻のターンを復元/sc-detail 14:23-14:30— 時刻範囲のターンをまとめて復元
何が返るか
- L2: そのターンの会話本文（ユーザー発言 + Claude 返答）
- L3: そのターンで実行されたツールの入出力
これは Throughline のセッション記憶 ~/.throughline/throughline.db から読み出されます。
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 · 23 lines · 31 tokens per session scan A 4781644e247e
sc-detail is a command published in the GitHub repository kitepon/Throughline (2 stars, last pushed 4d ago), licensed MIT. It adds 31 tokens to every session and 241 once invoked, about $0.0002 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 commands, from other repositories
orchestrate
Activate memory orchestrator mode for complex tasks.
memstack-search
Search MemStack memory for past sessions, insights, and project context.
memory-why
Show why a memory recall returned what it did -- BM25 vs vector vs hybrid provenance.
check
Run mneme check against a file or proposed change.
memory
Use when: user asks to remember something, after solving a non-obvious problem, or to capture key session findings.
update
Use when: search results seem noisy, after bulk imports, or for periodic memory/registry maintenance.