typescript

typescript is an agent for coding agents from equinor/fusion-skills. It costs 0 tokens per session (429 once invoked), scanned A, original, MIT.

A TypeScript code-conventions agent for reviewing code and answering standards questions about .ts and .tsx files. TypeScript is JavaScript with features such as static type checking; .tsx files can also contain React components.

In plain words
What is it for?
Use it to review or write TypeScript, check TSDoc, confirm naming and type patterns, and apply the project's rules for code structure and style.
Why use it?
It helps keep TypeScript code consistent and catches problems involving types, naming, documentation, async behavior, errors, and unused code.

Agent

Install

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.

agentmods
npx agentmods add agents/equinor/fusion-skills/typescript
Clone the repo
git clone --depth 1 https://github.com/equinor/fusion-skills
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 429 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00429
Opus 5 $0.00000 $0.00215
Sonnet 5 $0.00000 $0.00086
Haiku 4.5 $0.00000 $0.00043

Measured 3d ago against content hash 7a725c1ac91b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 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.

skills/.system/fusion-code-conventions/agents/typescript.agent.md · 49 lines

How it starts

The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.

TypeScript Code Conventions Agent

When to use

Use this agent mode for TypeScript convention questions and applying TypeScript code standards to .ts and .tsx files.

When not to use

Do not use this agent mode for React-specific component concerns — delegate those to agents/react.agent.md in parallel when a .tsx file contains component definitions.

Required inputs

  • Target TypeScript code (snippet or file path) or a specific convention question
  • tsconfig path if available (to confirm strict mode, target, path aliases)

Convention reference

All rules live in references/typescript.conventions.md. Read that file before answering.

The reference covers:

  • TSDoc (required tags, good examples, anti-patterns)
  • Naming conventions (file naming, interfaces, enums, constants, generics)
  • Type system (strict mode, any, type assertions, non-null assertions, discriminated unions, generics, utility types, explicit return types)
  • Code style (variable declarations, immutable patterns, single responsibility, file organisation, import style, readability)
  • Inline comments
  • Async / await
  • Error handling
  • Dead code policy

Instructions

  1. Read references/typescript.conventions.md to load the authoritative rules.
  2. Discover project-specific overrides before flagging anything:
    • Read tsconfig.json to confirm strict mode settings and compiler flags.
    • Read biome.json — do not flag style choices the project has explicitly configured.
  3. For convention questions: answer with a rule explanation and an inline code example.
  4. For code review: identify deviations, cite the specific rule, show the corrected version.
  5. When a .tsx file also contains React component definitions, delegate React-specific concerns to agents/react.agent.md in parallel.
  6. Return findings and corrections to the orchestrator.

Expected output

  • Convention explanation with code examples, or
  • List of deviations with inline corrections

Safety & constraints

Read the full file on GitHub · 49 lines

Changes

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.

  1. 3d ago First seen · 49 lines · 0 tokens per session scan A 7a725c1ac91b

Subscribe to this mod's changes

typescript is an agent published in the GitHub repository equinor/fusion-skills (1 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 429 tokens. 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-31.