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 agentmods add skills/notque/vexjoy-agent/typescript-checknpx skills add notque/vexjoy-agent --skill typescript-checkgit clone --depth 1 https://github.com/notque/vexjoy-agentWrote 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/notque/vexjoy-agent/typescript-check)<a href="https://agentmods.dev/skills/notque/vexjoy-agent/typescript-check"><img src="https://agentmods.dev/badge/skills/notque/vexjoy-agent/typescript-check.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.00018 | $0.00598 |
| Opus 5 | $0.00009 | $0.00299 |
| Sonnet 5 | $0.00004 | $0.00120 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
typescript-check 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 today.
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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript check
Read-only type validation. Follow repository instructions and package scripts; preserve project compiler settings. Do not fix code, change configuration, or install dependencies for a check-only request.
Run
- Locate
tsconfig.json, includingsrc/,app/, andpackages/. In a monorepo, use the package affected by the task or the repository's aggregate check. Ask only when the target cannot be inferred. If no config exists, report the missing configuration and stop. - Confirm TypeScript is installed locally before using npx; do not allow an implicit package download.
- Run
npx tsc --noEmit 2>&1, ornpx tsc --noEmit --project path/to/tsconfig.json 2>&1for a selected config. Capture output and exit code. Zero means pass; nonzero may mean type errors or a tool/configuration failure—report which. - Report status and error count. Group diagnostics by file and line, retaining
file:line:column,TS####, and the message. Retain complete logs; show useful failure details instead of all successful output.
Recovery and flags
- TypeScript missing: report it; suggest
npm install typescript --save-devwithin dependency setup. - npx missing: check
node --version; when Node/npm and local TypeScript exist, usenpm exec tsc -- --noEmit. Otherwise report the missing toolchain. - Multiple configs: list the checked configs and any omitted packages. A single-package pass is not a whole-repository pass.
--skipLibCheck: skips declaration-file checking; use only when configured or requested, not to hide failures.--strict: adds strict checks; enable only when requested or configured.--incremental: may write build-info cache files; enable only when permitted, not for a strictly read-only run.- Named files: passing files directly bypasses project config. Prefer
--project; do not claim equivalent coverage from a narrower check.
When running the full JavaScript/TypeScript check sequence, lint first, type-check next, then run tests with vitest-runner or the repository test command.
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.
- today Changed · -124 lines d679894b95ba
- 2d ago First seen · 170 lines · 18 tokens per session scan A 466067697202
typescript-check is a skill published in the GitHub repository notque/vexjoy-agent (420 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 598 once invoked, about $0.0001 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 skills, from other repositories
adk
Use this skill when you've got questions about the Botpress Agent Development Kit (ADK) - like when you're building a feature that involves tables, actions, tools, workflows, conversations, files, knowledge bases, triggers, or Zai.
typescript-patterns
TypeScript types: generics, discriminated unions, Zod, satisfies, branded types. Triggers: TypeScript, TS, generics, Zod, satisfies, strict mode.
typescript-rules
TypeScript/JavaScript coding rules: style, patterns, security, testing. Triggers: .ts, .tsx, .js, .jsx, package.json, tsconfig.json, React, Next.js, Vue, Vite, Vitest, Jest, ESLint.
valibot
Repository guidance for using Valibot as the schema validation library within the hr-skills monorepo. Use when writing or modifying schemas in packages/hr-skills-ref/src/schema.ts or packages/hr-skills-build/src/shared/schema.ts, when validating parsed YAML frontmatter, when handling safeParse results, or when…
typescript
Repository guidance for writing, reviewing, and maintaining TypeScript code within the hr-skills monorepo. Covers project conventions, compiler settings, module structure, and development workflows.
ai-infrastructure-ollama
Local LLM inference with the Ollama JavaScript client -- chat, streaming, tool calling, vision, embeddings, structured output, model management, and OpenAI-compatible endpoint.