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 zonlabs/mcp-ts --skill linkosgit clone --depth 1 https://github.com/zonlabs/mcp-tsWrote 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/zonlabs/mcp-ts/linkos)<a href="https://agentmods.dev/skills/zonlabs/mcp-ts/linkos"><img src="https://agentmods.dev/badge/skills/zonlabs/mcp-ts/linkos/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/zonlabs/mcp-ts/linkos"><img src="https://agentmods.dev/badge/skills/zonlabs/mcp-ts/linkos.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.00036 | $0.02453 |
| Opus 5.5 | $0.00014 | $0.00981 |
| Sonnet 5.5 | $0.00007 | $0.00491 |
| Haiku 4.5 | $0.00004 | $0.00245 |
Grade A, and why
linkos 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 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.
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 — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LinkOS
Use LinkOS when a task needs tools from connected MCP servers, especially when many possible servers or tools may be available. Prefer LinkOS's discovery and routing tools instead of loading every downstream MCP tool directly into the agent context.
LinkOS server:
https://mcp.linkos.in/mcp
User connection page:
https://app.linkos.in/mcp
What LinkOS Provides
LinkOS provides access to 100+ MCP servers such as GitHub, Notion, Zapier, Supabase, Exa, DeepWiki, Apify, Context7 and other connected services.
It exposes meta-tools for dynamic MCP discovery and a CodeMode tool that executes programs inside a secure sandbox for programmatic tool calling and result processing. Use this to avoid expensive LLM tool-calling loops when a task can be handled by discovering the right tools, inspecting only the needed schemas, executing a small program, and returning the final result.
Core Principle
Keep MCP tools discoverable, not always loaded.
Do not assume the agent needs every connected tool schema in context. Use LinkOS to search for the relevant capability, inspect only the needed schema, then execute the selected tool or workflow through the sandboxed runner.
Available LinkOS Tools
list_mcp_servers
List all currently connected upstream MCP servers and their indexed tool counts.
Use this to inspect which services are active or to filter by server name/ID:
query: "github" (optional filter)
search_mcp_tools
Search connected MCP servers for relevant tools.
Use this first when the task may require an external service such as GitHub, Notion, Slack, Gmail, Linear, Supabase, Exa, Zapier, cloud providers, databases, or any other connected MCP server.
Search with the user's goal, not just a tool name. For example:
find GitHub issues by label
post a message to Slack
search the web with Exa
create a Notion page
query Supabase rows
If no relevant tools are found, tell the user they likely need to connect the relevant MCP server at:
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 · 324 lines · 36 tokens per session scan A 85558ef0bf78
linkos is a skill published in the GitHub repository zonlabs/mcp-ts (23 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 2,453 once invoked, about $0.0001 per session on Opus 5.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-16.
linkos compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| linkoszonlabs/mcp-ts | Skill | 23 | 1mo ago | MIT | A | 36 | Claude Code, Codex |
| effect-developmentpingdotgg/t3code | Skill | 58k | today | MIT | A | 29 | Claude Code, Codex |
| effect-v4ComposioHQ/composio | Skill | 31k | today | MIT | A | 159 | Claude Code, Codex |
| chat-sdkvercel-labs/open-agents | Skill | 5.9k | 2mo ago | MIT | A | 191 | Claude Code, Codex |
| teams-sdk-to-agents-sdk-typescript-migrationmicrosoft/Agents | Skill | 1.1k | yesterday | MIT | A | 62 | Claude Code |
| decocms-uidecocms/studio | Skill | 419 | today | MIT | A | 95 | Claude Code |
| jira-releasedecocms/studio | Skill | 419 | today | MIT | A | 60 | Claude Code |