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 mnlt/teleport --skill _templategit clone --depth 1 https://github.com/mnlt/teleportWrote 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/mnlt/teleport/_template)<a href="https://agentmods.dev/skills/mnlt/teleport/_template"><img src="https://agentmods.dev/badge/skills/mnlt/teleport/_template/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/mnlt/teleport/_template"><img src="https://agentmods.dev/badge/skills/mnlt/teleport/_template.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.00055 | $0.00818 |
| Opus 5.5 | $0.00022 | $0.00327 |
| Sonnet 5.5 | $0.00011 | $0.00164 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade B, and why
{{service-id}} scanned grade B with 2 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 1mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
**Do NOT suggest editing `~/.claude/settings.local.json` manually.** `teleport-setup add-key` handles it with backup, validation, and masked input. Stop execution until the user has run the command and restarted. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sL -H "Authorization: Bearer ${{ENV_VAR}}" \ How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{{Service}}
Operates {{Service}} via its public REST API. No MCP server required — bypasses directly via HTTP.
Credentials check
[ -n "${{ENV_VAR}}" ] && echo "{{ENV_VAR}}: PRESENT" || echo "{{ENV_VAR}}: MISSING"
Never echo the variable directly.
If MISSING, respond to the user with EXACTLY this message (do NOT paraphrase, do NOT suggest manual JSON edits):
I need your {{service-id}} credential. Run this in another terminal — it'll open the signup page, validate format, and save it safely with masked input:
teleport-setup add-key {{service-id}}Then restart Claude Code (
/exit, thenclaude) and ask me again.
Do NOT suggest editing ~/.claude/settings.local.json manually. teleport-setup add-key handles it with backup, validation, and masked input. Stop execution until the user has run the command and restarted.
API
- Base URL:
{{https://api.service.com/v1}} - Auth header:
Authorization: Bearer ${{ENV_VAR}} - Extra headers:
{{Accept: application/json}}
Common patterns
# {{Describe operation 1 — e.g. List items}}
curl -sL -H "Authorization: Bearer ${{ENV_VAR}}" \
"{{base_url}}/{{resource}}"
# {{Describe operation 2 — e.g. Get one item}}
curl -sL -H "Authorization: Bearer ${{ENV_VAR}}" \
"{{base_url}}/{{resource}}/{id}"
# {{Describe operation 3 — e.g. Create item}}
curl -sL -X POST \
-H "Authorization: Bearer ${{ENV_VAR}}" \
-H "Content-Type: application/json" \
"{{base_url}}/{{resource}}" \
-d '{"key":"value"}'
# {{Describe operation 4 — e.g. Update item}}
curl -sL -X PATCH \
-H "Authorization: Bearer ${{ENV_VAR}}" \
-H "Content-Type: application/json" \
"{{base_url}}/{{resource}}/{id}" \
-d '{"key":"new-value"}'
# {{Describe operation 5 — e.g. Delete item}}
curl -sL -X DELETE \
-H "Authorization: Bearer ${{ENV_VAR}}" \
"{{base_url}}/{{resource}}/{id}"
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.
- 1mo ago First seen · 83 lines · 0 tokens per session scan B bbeb0e877cce
{{service-id}} is a skill published in the GitHub repository mnlt/teleport (8 stars, last pushed 5mo ago), licensed MIT. It adds 55 tokens to every session and 818 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
save-learning
Saves user instructions as persistent learnings for future sessions. Use when the user says 'remember this', 'always do X', 'from now on', 'never do Y', or gives any instruction they want persisted across sessions. Proactively suggest when the user states a preference, convention, or rule they clearly want followed in…
web-access
A method for handling difficult web tasks across search, page fetching, and a real browser. It covers sites that need login sessions, dynamic pages, anti-bot handling, or exploration before their structure is understood.
skill-creator
A skill for creating or improving reusable instructions for an agent. It covers capturing the intended workflow, writing a draft, testing it, and refining its trigger description.
repo
Repository operating rules for verified Mythos edits.
lc-curate-context
Decide which files a task actually needs, record that as a reusable llm-context rule, verify it against the codebase - including the files your selection references but leaves out - and pack it for your own context, a chat, or a sub-agent you dispatch. Load when choosing what code to put in front of a model, packing…
atomic-tdd
Test-first discipline. Auto-triggers on "let's implement X", "add feature Y", "fix bug Z", "write a test for", "implement", "build out", and similar pre-code-change phrases. Iron rule: failing test exists before production code. Skip only for pure docs/config changes with an explicit "skipped because:" note. Explicit…