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 glidermcp/glidermcp.com --skill tglider-typescriptgit clone --depth 1 https://github.com/glidermcp/glidermcp.comWrote 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/glidermcp/glidermcp.com/tglider-typescript)<a href="https://agentmods.dev/skills/glidermcp/glidermcp.com/tglider-typescript"><img src="https://agentmods.dev/badge/skills/glidermcp/glidermcp.com/tglider-typescript.svg" alt="Measured on agentmods" 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.00032 | $0.00262 |
| Opus 5 | $0.00016 | $0.00131 |
| Sonnet 5 | $0.00006 | $0.00052 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
tglider-typescript 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 7d 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.
What it actually says
TGlider TypeScript Workflow
Use TGlider when working in a TypeScript or JavaScript repository and the task needs semantic facts rather than plain text search.
Start by loading the relevant workspace when needed. Prefer semantic symbol, reference, export, diagnostic, hierarchy, call graph, impact, and dependency tools before reading source text. Use source reads only for bounded context after the semantic tools identify the relevant files or symbols.
For edits, gather evidence first with tools for references, callers, outgoing calls, diagnostics, dependency topology, and change impact. Prefer preview-first refactoring tools where available, and refresh diagnostics after meaningful edits.
For non-code assets, generated output, literal config files, and repo-wide text search, prefer Scout's find when Scout is installed. TGlider's own search_text searches with Scout and requires it - without a scout binary on PATH it returns a scout_not_installed hint, so install Scout globally to use that tool at all. Use shell text search when Scout is absent, or when neither can answer the question.
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.
- 7d ago First seen · 15 lines · 32 tokens per session scan A 340b9e95a832
tglider-typescript is a skill published in the GitHub repository glidermcp/glidermcp.com (16 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 262 once invoked, about $0.0002 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-30.
Other skills, from other repositories
no-bare-casts
Writing as in TypeScript or TSX production code, modifying a file that contains a bare as cast, silencing a type error with a cast, encountering as unknown as, or reviewing a cast site.
code-review-typescript
Deep TypeScript-specific code review covering type safety, ESM/CJS, async correctness, money precision, and domain modeling. Applied in addition to the generic code-review skill when TypeScript/JavaScript code is detected. Invoked when reviewing TS/JS PRs, TypeScript changes, or performing TypeScript-specific quality…
eslint-config
Composable ESLint flat config for TypeScript projects. Use config() with presets.base spread to activate baseline, javascript, typescript, imports, jsdoc, unicorn, perfectionist, prettier, regexp, command, packagejson, pnpm, gitignore, node, e18e configs. autoEnable detects installed packages (astro, svelte, lit…
effective-typescript
Review existing TypeScript code and write new TypeScript following the 62 items from "Effective TypeScript" by Dan Vanderkam. Use when writing TypeScript, reviewing TypeScript code, working with type design, avoiding any, managing type declarations, or migrating JavaScript to TypeScript. Trigger on: "TypeScript best…
biome
Biome - Fast all-in-one toolchain for web projects (linter + formatter in Rust, 100x faster than ESLint).
migrate-oxfmt
Guide for migrating a project from Prettier or Biome to Oxfmt. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's formatter from Prettier or Biome to Oxfmt.