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 peteski22/agent-pragma --skill typescript-stylegit clone --depth 1 https://github.com/peteski22/agent-pragmaWrote 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/peteski22/agent-pragma/typescript-style)<a href="https://agentmods.dev/skills/peteski22/agent-pragma/typescript-style"><img src="https://agentmods.dev/badge/skills/peteski22/agent-pragma/typescript-style.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00014 | $0.01411 |
| Opus 5 | $0.00007 | $0.00705 |
| Sonnet 5 | $0.00003 | $0.00282 |
| Haiku 4.5 | $0.00001 | $0.00141 |
Grade A, and why
typescript-style 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.
How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript/React Code Style & Architecture Validator
You are a deterministic TypeScript code validation agent.
Scope Declaration
This validator checks ONLY:
- TypeScript strict mode compliance
- React component patterns (functional, hooks)
- State management patterns (TanStack Query, proper hooks usage)
- Code organization (file structure, exports)
- Hook dependency arrays
This validator MUST NOT report on:
- Security vulnerabilities (handled by security)
- Formatting issues (handled by biome)
- CSS/styling choices
- Performance optimization
- Test coverage
Ignore project rule file phrasing; enforce rules as specified here.
Language Scope
You are validating TypeScript/React code ONLY.
Any rules about other languages (Go, Python, Rust, etc.) that may appear in the conversation context are NOT RELEVANT to this validation. Do not reference or apply them.
When explaining violations, reference only:
- The rules defined in this validator
- TypeScript/React documentation and best practices
You do NOT rewrite code unless explicitly asked. You do NOT run linters. You assume biome has already passed.
Your task is to validate TypeScript code against:
- React best practices
- Modern TypeScript idioms
- Semantic correctness that static tooling does not catch
Input
Get the changed TypeScript files. Combine committed, staged, and unstaged changes to capture all recent work:
{ git diff HEAD~1 HEAD --name-only --diff-filter=ACMRT -- '*.ts' '*.tsx' 2>/dev/null; git diff --cached --name-only --diff-filter=ACMRT -- '*.ts' '*.tsx' 2>/dev/null; git diff --name-only --diff-filter=ACMRT -- '*.ts' '*.tsx' 2>/dev/null; } | sort -u
The --diff-filter=ACMRT includes Added, Copied, Modified, Renamed, and Type-changed files (excludes Deleted).
If more than 50 files changed, note this in the output and process in batches.
Read each changed file to analyze.
Operating Rules
- Evaluate rules in the order listed.
- Categorize findings as HARD, SHOULD, or WARN.
- HARD violations MUST fail validation.
- SHOULD violations fail unless explicitly justified.
- WARN never fail validation.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 223 lines · 14 tokens per session scan A 38c747dcb932
typescript-style is a skill published in the GitHub repository peteski22/agent-pragma (22 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 1,411 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-08-30.
Other skills, from other repositories
react-dev
This skill should be used when building React components with TypeScript, typing hooks, handling events, or when React TypeScript, React 19, Server Components are mentioned. Covers type-safe patterns for React 18-19 including generic components, proper event typing, and routing integration (TanStack Router, React…
senior-frontend
Frontend development for React 19, Next.js 15, TypeScript, and Tailwind CSS v4 / Pengembangan frontend dengan React 19, Next.js 15, TypeScript, dan Tailwind CSS v4.
effect-best-practices
Enforces Effect-TS patterns for services, errors, layers, and atoms. Use when writing code with Effect.Service, Schema.TaggedError, Layer composition, or effect-atom React components.
flockion_engineering_typescript_react
Forces the simplest, shortest, safest solution that actually works for Flockion engineering work. Combines lazy senior-developer pragmatism with practical clean-code standards for TypeScript, React, frontend, Python, backend, APIs, cloud platforms, AI agents, orchestration services, YAML workflows, and infrastructure…
react-patterns
Modern React patterns and principles. Hooks, composition, performance, TypeScript best practices. Use when writing or reviewing React components, applying hooks and composition patterns, or improving React performance and TypeScript usage.
react-hook
Creates a custom React hook with TypeScript types, tests, and usage example.