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/davidruzicka/mcp4openapi/typescript-es2022npx skills add davidruzicka/mcp4openapi --skill typescript-es2022git clone --depth 1 https://github.com/davidruzicka/mcp4openapiWrote 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/davidruzicka/mcp4openapi/typescript-es2022)<a href="https://agentmods.dev/skills/davidruzicka/mcp4openapi/typescript-es2022"><img src="https://agentmods.dev/badge/skills/davidruzicka/mcp4openapi/typescript-es2022.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 | $0.00050 | $0.00918 |
| Opus 5 | $0.00025 | $0.00459 |
| Sonnet 5 | $0.00010 | $0.00184 |
| Haiku 4.5 | $0.00005 | $0.00092 |
Grade A, and why
typescript-es2022 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript 5.x ES2022
Core intent
- Respect existing architecture and coding standards.
- Prefer readable, explicit solutions over clever shortcuts.
- Extend current abstractions before inventing new ones.
- Prioritize maintainability and clarity.
General guardrails
- Target TypeScript 5.x / ES2022 and prefer native features over polyfills.
- Use pure ES modules; never emit CommonJS patterns.
- Rely on project build, lint, and test scripts unless asked otherwise.
- Note design trade-offs when intent is not obvious.
Project organization
- Follow repository folder and responsibility layout for new code.
- Use kebab-case filenames unless told otherwise.
- Keep tests, types, and helpers near implementation when it improves discoverability.
- Reuse shared utilities before adding new ones.
- Prefer existing helpers in
src/validation/validation-utils.tsfor reusable validation/security checks (for example own-property checks) instead of ad-hoc inline logic.
Naming and style
- Use PascalCase for classes, interfaces, enums, and type aliases; camelCase for everything else.
- Exception: snake_case is permitted for DTOs, API contracts, and configuration files where external formats dictate it.
- Skip interface prefixes like
I. - Name things for behavior or domain meaning, not implementation details.
Formatting and style
- Run repository lint/format scripts where defined.
- Match project formatting conventions.
- Keep functions focused; extract helpers when branching grows.
- Favor immutable data and pure functions when practical.
Type system expectations
- Avoid
any; preferunknownplus narrowing. - Use discriminated unions for event/state flows.
- Centralize shared contracts instead of duplicating shapes.
- Use utility types (
Readonly,Partial,Record) to express intent.
Async, events, and error handling
- Use async/await.
- Guard edge cases early to avoid deep nesting.
- Send errors through project logging/telemetry utilities.
- Surface user-facing errors via repository patterns.
- Debounce config-driven updates and dispose resources deterministically.
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 · 101 lines · 50 tokens per session scan A 284c77560734
typescript-es2022 is a skill published in the GitHub repository davidruzicka/mcp4openapi (0 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 918 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…