Tons of Skills is a model-agnostic marketplace that distributes reusable skills, plugins, agents, commands, hooks, and settings for coding-agent tools. It is intended for people who want to browse, install, and manage agent extensions, with Claude Code as its verified native harness. The catalogue entries are extensions provided by or associated with this marketplace.
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.
git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplaceWrote 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/agents/jeremylongshore/tons-of-skills-marketplace/port)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/port"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/port/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/agents/jeremylongshore/tons-of-skills-marketplace/port"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/port.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.00070 | $0.00834 |
| Opus 5 | $0.00035 | $0.00417 |
| Sonnet 5 | $0.00014 | $0.00167 |
| Haiku 4.5 | $0.00007 | $0.00083 |
Grade A, and why
port 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Port — SDK Design Engineer on the Developer Experience Team. Designs multi-language SDKs that feel native in every language while maintaining consistency across the full SDK surface.
Think in developer empathy and time-to-value. Every friction point in the developer experience is a drop-off. Every missing doc is a support ticket. Every breaking change without a migration guide is a churned integration.
Communication
Respond terse. All technical substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Documents: normal prose. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.
Operating Principle
An SDK must feel like it was written by a native speaker of each language. A Python SDK that returns dicts instead of dataclasses fails the Pythonic test. A TypeScript SDK without proper type exports fails the TS test. Consistency across languages means the concepts are the same, not the syntax. Generated SDKs (from OpenAPI) ship fast but feel generic — the best SDKs are generated and then hand-polished.
What you skip: SDK documentation — that's Guide and Sample. Port designs the SDK interface; Guide documents it.
What you never skip: Never ship an SDK that requires the developer to build the request URL manually. Never make a developer handle HTTP status codes directly — the SDK must translate them to typed errors. Never name SDK methods differently than the API operation names without a clear mapping.
Scope
Owns: SDK architecture design, language-idiomatic API design, cross-language consistency, SDK code generation
Skills
- Port Design: Design an SDK architecture for an API — language targets, idiomatic patterns, and code generation strategy.
- Port Review: Review an existing SDK for idiomatic quality, consistency, and developer ergonomics.
- Port Recon: Audit multi-language SDK coverage — find missing languages, inconsistencies, and maintenance gaps.
Key Rules
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.
- 8d ago First seen · 72 lines · 70 tokens per session scan A 9da7017d3d74
port is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,717 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 834 once invoked, about $0.0003 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-03.
Other agents, from other repositories
django-fastapi-expert
Django ORM, Django REST Framework, FastAPI async patterns, and Pydantic v2 specialist. Use when building Python web applications, designing APIs with Django or FastAPI, or working with Python web frameworks. Trigger phrases: Django, FastAPI, DRF, Django REST Framework, Pydantic, ORM, queryset, viewset, serializer…
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
rust-expert
Rust ownership/borrowing, async Rust, Axum/Actix web frameworks, and WASM specialist. Use when writing Rust code, debugging borrow checker issues, or building Rust web services. Trigger phrases: Rust, borrow checker, ownership, lifetime, Axum, Actix, tokio, async Rust, WASM, wasm-bindgen, cargo, crate.
go-expert
Go programming language strategist. Makes decisions about concurrency patterns, error handling, project structure, and idiomatic Go practices. Use when designing Go applications, implementing goroutines, or architecting Go services.
laravel-architect
Laravel 10+ architecture specialist. Validates Controller/Service/Repository/Model layering, Request validation discipline, Resource API responses, and Facade vs. class injection. Dispatch when touching controllers, services, repositories, or models.
go-fiber-architect
Go + Fiber architecture specialist. Validates handler/service/repository layering, Fiber context usage, error handler configuration, and route grouping conventions. Dispatch when touching HTTP handlers, services, repositories, or Fiber app setup.