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 gleanwork/configure-agents --skill api-client-typescriptgit clone --depth 1 https://github.com/gleanwork/configure-agentsWrote 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/gleanwork/configure-agents/api-client-typescript)<a href="https://agentmods.dev/skills/gleanwork/configure-agents/api-client-typescript"><img src="https://agentmods.dev/badge/skills/gleanwork/configure-agents/api-client-typescript/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/gleanwork/configure-agents/api-client-typescript"><img src="https://agentmods.dev/badge/skills/gleanwork/configure-agents/api-client-typescript.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.00066 | $0.00657 |
| Opus 5.5 | $0.00026 | $0.00263 |
| Sonnet 5.5 | $0.00013 | $0.00131 |
| Haiku 4.5 | $0.00007 | $0.00066 |
Grade A, and why
glean-api-client 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 3d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@gleanwork/api-client-typescript
The official TypeScript SDK for the Glean API. It is generated from Glean's OpenAPI spec, so it is fully typed and the types are the source of truth.
This file is a worked example for the authoring rubric. It demonstrates the pattern — point at the generated types, then carry only judgment — not a maintained skill.
When to use
Load this skill when writing TypeScript or JavaScript that calls the Glean API — search, chat/assistant, document retrieval, indexing, or admin endpoints — or whenever @gleanwork/api-client-typescript appears in the code.
Install & import
npm install @gleanwork/api-client-typescript
import { Glean } from '@gleanwork/api-client-typescript';
Authoritative API
The API surface is generated and fully typed. Read the bundled type definitions for exact method names, parameters, request/response shapes, and enums — do not guess them:
- the
.d.tsfiles referenced by thetypes/exportsfield innode_modules/@gleanwork/api-client-typescript/package.json(underdist/).
Operations hang off the client instance; the exact namespaces and signatures live in the types. Let editor autocomplete and the .d.ts drive the call shape rather than memorized examples.
Usage patterns
- Construct once, reuse. Create a single
Gleanclient configured with your API token and instance / server URL, and pass it around. Don't build one per request. - Authentication. Supply the API token and the Glean instance (or full server URL) at construction. Read the constructor's options type for the exact field names.
- Pagination. List endpoints are cursor-based: pass the cursor from the previous response on the next call and stop when none is returned. Don't assume offset paging.
- Errors. Failures throw typed errors. Catch them and inspect the typed fields instead of parsing message strings.
Common mistakes
- Guessing method names or parameter shapes. They are generated — read the
.d.ts. Hallucinated method names are the most common failure. - Scattering the instance / server URL across the codebase instead of centralizing it in client construction.
- Ignoring pagination cursors and treating the first page as the full result set.
- Catch-and-stringify error handling instead of using the typed error fields.
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.
- 3d ago First seen · 51 lines · 66 tokens per session scan A d4fd4098d2a2
glean-api-client is a skill published in the GitHub repository gleanwork/configure-agents (2 stars, last pushed 3d ago), licensed MIT. It adds 66 tokens to every session and 657 once invoked, about $0.0003 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-10-13.
Other skills, from other repositories
adapter-express
Mount tRPC as Express middleware with createExpressMiddleware() from @trpc/server/adapters/express. Access Express req/res in createContext via CreateExpressContextOptions. Mount at a path prefix like app.use('/trpc', ...). Avoid global express.json() conflicting with tRPC body parsing for FormData.
trpc-router
Entry point for all tRPC skills. Decision tree routing by task: initTRPC.create(), t.router(), t.procedure, createTRPCClient, adapters, subscriptions, React Query, Next.js, links, middleware, validators, error handling, caching, FormData.
stripe-projects
Use after E2B sandbox/API access has been provisioned through Stripe Projects and the user needs to use the resulting E2B API key with the E2B CLI, JavaScript SDK, Python SDK, or Code Interpreter SDK.
nestjs-expert
Creates and configures NestJS modules, controllers, services, DTOs, guards, and interceptors for enterprise-grade TypeScript backend applications. Use when building NestJS REST APIs or GraphQL services, implementing dependency injection, scaffolding modular architecture, adding JWT/Passport authentication, integrating…
chat-sdk
Build multi-platform chat bots with Chat SDK (chat npm package). Use when developers want to (1) Build a Slack, Teams, Google Chat, Discord, Telegram, GitHub, Linear, or WhatsApp bot, (2) Use Chat SDK to handle mentions, direct messages, subscribed threads, reactions, slash commands, cards, modals, files, or AI…
fastify-best-practices
Guides development of Fastify Node.js backend servers and REST APIs using TypeScript or JavaScript. Use when building, configuring, or debugging a Fastify application — including defining routes, implementing plugins, setting up JSON Schema validation, handling errors, optimising performance, managing authentication…