teleport-from

teleport-from is a skill for Claude Code from seilk/claude-teleport. It costs 12 tokens per session (431 once invoked), scanned A, original, MIT.

A guided importer for copying selected agent settings from another user’s public Claude configuration repository. It lets you choose a machine and individual agents, rules, or skills to import.

In plain words
What is it for?
Use it to browse another user’s published configurations, select useful parts, and copy them into your own Claude configuration.
Why use it?
It avoids manually finding, copying, and reviewing configuration files from someone else’s repository. It also scans selected files before they are imported.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; names the AskUserQuestion tool.

Part of the claude-teleport plugin — 7 skills shipped together

Good fit Use it to browse another user’s published configurations, select useful parts, and copy them into your own Claude configuration.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/seilk/claude-teleport/teleport-from
Install

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.

Any agent
npx skills add seilk/claude-teleport --skill teleport-from
Clone the repo
git clone --depth 1 https://github.com/seilk/claude-teleport

Made for: Claude Code.

Or install claude-teleport, the plugin that ships this one along with the rest of its 7 skills.

Wrote 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.

agentmods badge for teleport-from

README.md
[![agentmods](https://agentmods.dev/badge/skills/seilk/claude-teleport/teleport-from/github.svg)](https://agentmods.dev/skills/seilk/claude-teleport/teleport-from)
Your own site
<a href="https://agentmods.dev/skills/seilk/claude-teleport/teleport-from"><img src="https://agentmods.dev/badge/skills/seilk/claude-teleport/teleport-from/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.

agentmods 80×15 button for teleport-from

Your own site · 80×15
<a href="https://agentmods.dev/skills/seilk/claude-teleport/teleport-from"><img src="https://agentmods.dev/badge/skills/seilk/claude-teleport/teleport-from.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 431 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00012 $0.00431
Opus 5 $0.00006 $0.00216
Sonnet 5 $0.00002 $0.00086
Haiku 4.5 $0.00001 $0.00043

Measured 11d ago against content hash 3398601574e3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

teleport-from 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 11d 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.

skills/teleport-from/SKILL.md · 35 lines

What it actually says

Teleport From

Import configurations from another user's public teleport repo.

Steps

  1. Clone public repo: Clone <username>/claude-teleport-public to a temp directory. The repo contains an agent-friendly README.md that describes the repository structure and import instructions.

  2. List machines: Read registry.yaml from the cloned repo to list available machines and their config counts. Use AskUserQuestion (single-select) to let the user pick a machine. Options: each machine name with config counts as description (e.g. "macbook-pro (3 agents, 5 rules)"), plus "main (merged union of all machines)".

  3. Read machine configs: Read files from machines/<selected-alias>/ in the repo. Present categories: "Available: X agents, Y rules, Z skills." File paths inside machines/<alias>/ map directly to ~/.claude/ paths.

  4. User selects: Use AskUserQuestion with multiSelect: true to present available categories. Then for each selected category, use another AskUserQuestion with multiSelect: true listing specific items.

  5. Mandatory content review: For ALL selected files (not just hooks):

    • Run rce-scan --file <path> on each.
    • Show full file content to the user.
    • If RCE patterns found: highlight flagged lines.
    • User must explicitly approve each file: "I've reviewed this, apply it."
  6. Backup: Run backup --claude-dir ~/.claude. Show backup path.

  7. Apply: Apply selected items using the apply command.

  8. Show result: Display what was applied, any errors, and plugin install instructions.

  9. Cleanup: Remove temp directory.

Changes

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.

  1. 11d ago First seen · 35 lines · 12 tokens per session scan A 3398601574e3

Subscribe to this mod's changes

teleport-from is a skill published in the GitHub repository seilk/claude-teleport (6 stars, last pushed 3mo ago), licensed MIT. It adds 12 tokens to every session and 431 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens