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/samplexbro/agentsmesh/typescript-quality-gatesnpx skills add sampleXbro/agentsmesh --skill typescript-quality-gatesgit clone --depth 1 https://github.com/sampleXbro/agentsmeshWrote 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/samplexbro/agentsmesh/typescript-quality-gates)<a href="https://agentmods.dev/skills/samplexbro/agentsmesh/typescript-quality-gates"><img src="https://agentmods.dev/badge/skills/samplexbro/agentsmesh/typescript-quality-gates.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.00033 | $0.00694 |
| Opus 5 | $0.00016 | $0.00347 |
| Sonnet 5 | $0.00007 | $0.00139 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
typescript-quality-gates 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 2d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
TypeScript Quality Gates
You are responsible for enforcing high-confidence quality gates for a production TypeScript library.
Goals
- Catch correctness, typing, packaging, and compatibility issues before release.
- Keep CI fast but meaningful.
- Prevent invalid declaration output and broken package metadata.
- Enforce standards that matter for consumers, not cosmetic noise.
Required baseline checks
Every substantial change should be evaluated against these gates:
-
Typecheck
tsc --noEmitor equivalent project validation- zero unresolved type errors
-
Build
- production build succeeds
- declaration files emit correctly
- output structure matches
package.jsonexports
-
Lint
- enforce correctness-focused linting
- avoid excessive stylistic churn unless the repo explicitly wants it
-
Tests
- unit/integration/type tests pass
-
Package verification
- inspect the packed artifact using
npm pack --dry-runor equivalent - confirm only intended files ship
- verify README, LICENSE, declaration files, and dist outputs are present
- inspect the packed artifact using
tsconfig expectations
Prefer strict settings for libraries.
Recommended expectations:
strict: truenoImplicitOverride: truewhere applicablenoUncheckedIndexedAccess: truewhen practicalexactOptionalPropertyTypes: truewhen the API benefits from tighter semanticsdeclaration: truedeclarationMap: truewhen useful for debuggingsourceMap: truefor distributed debugging if desiredskipLibCheckmay be tolerated for CI speed, but do not use it to hide library issues in authored code
Declaration quality rules
Validate that emitted .d.ts files:
- resolve successfully for consumers
- do not reference private/internal paths
- do not leak unstable implementation details unnecessarily
- align with documented public API
- remain readable enough for IDE usage
Packaging integrity rules
Check:
exportsmap matches real filestypespath exists and is correctbintargets exist and are executable when applicablefileswhitelist is accuratesideEffectsis correctenginesreflects actual compatibility
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.
- 2d ago First seen · 111 lines · 33 tokens per session scan A 7deae185cdfb
typescript-quality-gates is a skill published in the GitHub repository sampleXbro/agentsmesh (24 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 694 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-09-03.
Other skills, from other repositories
ultracite
Ultracite is a zero-config linting and formatting preset for JavaScript/TypeScript projects. Use when: (1) Setting up or initializing Ultracite in a project (ultracite init), (2) Running linting or formatting commands (check, fix, doctor), (3) Writing or reviewing JS/TS code in a project that uses Ultracite — to…
microsoft-typescript
TypeScript is a language for application scale JavaScript development. ALWAYS use when editing or working with .ts, .tsx, .mts, .cts files or code importing "typescript". Consult for debugging, best practices, or modifying typescript, TypeScript.
bombshell-dev-clack
ALWAYS use when writing code importing "@clack/prompts". Consult for debugging, best practices, or modifying @clack/prompts, clack/prompts, clack prompts, clack.
jest-unit
Unit testing skill using Jest for TypeScript and JavaScript, covering mocking, spies, snapshots, coverage, async testing, and custom matchers.
enums
TypeScript enum conventions for the Playwright scaffold — PascalCase enum names, SCREAMINGSNAKECASE members, location rules for app-specific (enums/{area}/) vs shared/utility (enums/util/) constants, and the rules for adding or extending enums. Use when adding a new API endpoint path, UI message, role, storage-state…
refactor-values
Safe refactoring workflow for enum values, enum keys, and static test data in test-data/static/.ts — mandatory impact analysis, cascading updates, and verification. Use BEFORE changing any enum member's string value (ApiEndpoints., Messages., Roles, StorageStatePaths), renaming any enum key, or editing any existing…