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/cukas/remembrall/lineagegit clone --depth 1 https://github.com/cukas/remembrallWrote 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/cukas/remembrall/lineage)<a href="https://agentmods.dev/commands/cukas/remembrall/lineage"><img src="https://agentmods.dev/badge/commands/cukas/remembrall/lineage.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.00014 | $0.00132 |
| Opus 5 | $0.00007 | $0.00066 |
| Sonnet 5 | $0.00003 | $0.00026 |
| Haiku 4.5 | $0.00001 | $0.00013 |
Grade A, and why
lineage 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 4d 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
Session Lineage
Run the lineage script to display the session ancestry graph:
bash "$CLAUDE_PLUGIN_ROOT/scripts/remembrall-lineage.sh" "$(pwd)"
Show the output to the user as-is. The script renders a text DAG showing:
- Session chains (parent → child relationships)
- Time-Turner branches (parallel agents)
- Session status (active, completed, interrupted, merged)
- Files touched per session
If no lineage data exists yet, inform the user that lineage is recorded automatically as they work.
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.
- 4d ago First seen · 21 lines · 14 tokens per session scan A 8dde27f9cd61
lineage is a command published in the GitHub repository cukas/remembrall (6 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 132 once invoked, about $0.0001 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
handoff-resume
Resume from a prior session's handoff in .handoffs/.
handoff
Write a session handoff to .handoffs/ before context runs out.
composite-actions
Generate, review, secure, and test composite GitHub Actions following best practices — full repo scaffold, interview-driven generation, PR creation on existing repos, SHA pinning, secrets-as-inputs, job summaries, and actionlint validation.
datadog
Set up and troubleshoot Datadog — Agent deployment on Kubernetes, APM instrumentation, Log Management, Monitors, Dashboards, SLOs, Synthetic tests, and live incident investigation using the Datadog MCP server. Covers Terraform-managed Datadog resources.
linkerd
Linkerd-specific diagnostics — mTLS verification, proxy injection issues, authorization policy debugging, traffic management, and multi-cluster connectivity problems.
announce
Draft X/Twitter announcement post (or thread) for the latest plugin release.