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 sonichi/sutando --skill import-claude-contextgit clone --depth 1 https://github.com/sonichi/sutandoWrote 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/sonichi/sutando/import-claude-context)<a href="https://agentmods.dev/skills/sonichi/sutando/import-claude-context"><img src="https://agentmods.dev/badge/skills/sonichi/sutando/import-claude-context/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/sonichi/sutando/import-claude-context"><img src="https://agentmods.dev/badge/skills/sonichi/sutando/import-claude-context.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.00229 | $0.10597 |
| Opus 5 | $0.00114 | $0.05299 |
| Sonnet 5 | $0.00046 | $0.02119 |
| Haiku 4.5 | $0.00023 | $0.01060 |
Grade A, and why
import-claude-context 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 today.
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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Import Claude context
Sutando starts out knowing the owner's projects, decisions, open threads and people by reading the conversations they already had with Claude Code. The transcripts under the stock ~/.claude/projects/ (claude_home_path("projects", vanilla=True) — never Sutando's relocated .claude-sutando) are indexed without a model, the dialog is cleaned and redacted on disk, cheap-model subagents summarise it, the result is staged and shown to the owner as a digest, and only their "bring it in" moves it into the Sutando-owned sinks.
Usage: /import-claude-context [--projects a,b] [--session uuid] [--since 30d] [--dry-run] [--counts-only] [--json] [--new] [--cloud] [--stage [--known-people file]] [--commit] [--discard] [--forget slug] [--include date|uuid] [--include-personal] [--hold date|uuid] [--forget-session date|uuid] [--purge-dumps]
When it runs
- Owner ask (any install, standalone or desktop) — the owner says "import my Claude history", "read my Claude Code sessions", the Settings button's sentence "Import my Claude Code history, consented in Settings at .", or invokes
/import-claude-context. Same procedure with--run-kind user. - AG2 Space desktop onboarding — the owner's first-contact DM message carries the import request when they consented on the onboarding card: "Hi — I'm all set up, say hello. Then import my Claude Code history: I consented on the onboarding card at , N conversations across M projects." The trigger is an owner message containing "import my Claude Code history" together with "consented on the onboarding card at ". Run the procedure below with
--run-kind onboarding; the message's counts are the card's file count, the acknowledgement uses the index'sconversations(step 2). Legacy / fallback: an earlier desktop wrote the same request as its own task file —channel_id: onboarding-wizard,user_id: onboarding-wizard,access_tier: owner,priority: low, body "Run the import-claude-context skill (onboarding run). Consent given on the onboarding card at …" — and installed clients may still do so; treat that task exactly as this case (it is consented;priority: loworders it after a pending greeting and defers nothing — seesrc/task_priority.py). Its result is[no-send](the wizard channel has no delivery path). A queued import task is never left intasks/for a later turn:/task-orphan-checkstep 3a keeps a started one out of the recovery DM (a started run whosestatus.jsonhas not moved for an hour is listed there as stalled, and still resumes on the next sweep), but only this procedure starts it. - Review reply — while
$DATA/staged/review.mdexists, an owner message saying "bring it in", "bring in ", "forget ", "include ", "include personal", "hold " or "forget " answers the pending review: run the matching command from step 10 and nothing else. Any other message is not an answer; the set stays staged. The owner may ask what a held session was about: answer in the owner DM only, on request, from the summary — answering does not include it.
What ships with it
8 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.
- today First seen · 145 lines · 229 tokens per session scan A a3e11e6a8344
import-claude-context is a skill published in the GitHub repository sonichi/sutando (394 stars, last pushed today), licensed MIT. It adds 229 tokens to every session and 10,597 once invoked, about $0.0011 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-09-12.
Other skills, from other repositories
vellum-memory-v3-migration
One-time migration of an existing memory-v2 concept corpus into the memory-v3 section-grain "wiki" — topical articles with a stand-alone lead and queryable sections — with loss-proof staging, assistant-reviewed authoring, and a retrieval-eval gate before cutover.
vellum-memory-v2-migration
Perform a one-time migration from memory v1, to memory v2, which was introduced in 0.8.0.
daily-briefing
Proactive daily briefing that fires on a recurring schedule, pulls recent memory and workspace context, composes a structured summary (action items, progress, radar, next steps), and delivers it to all active channels. Enable with a time like "set up my daily briefing at 9am". Disable, reschedule, or check status at…
loci
Memory Palace for AI — persistent structured memory, identity, and task management across every conversation.
openclaw-lite
On first message, check if /.loci/lite/tasks/active.md exists.
memory-corpus-ingest
Ingest a large dataset into memory as a skimmed map. Cold-store the raw files under a workspace imports directory, census them into a slice plan, skim each slice into compact map pages that point back at the raw files, ingest the map with the memory ingest CLI, and author a drill-in retrieval skill so the corpus stays…