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 vynazevedo/first-plan --skill lens-typescriptgit clone --depth 1 https://github.com/vynazevedo/first-planWrote 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/vynazevedo/first-plan/lens-typescript)<a href="https://agentmods.dev/skills/vynazevedo/first-plan/lens-typescript"><img src="https://agentmods.dev/badge/skills/vynazevedo/first-plan/lens-typescript.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.00059 | $0.01173 |
| Opus 5 | $0.00030 | $0.00587 |
| Sonnet 5 | $0.00012 | $0.00235 |
| Haiku 4.5 | $0.00006 | $0.00117 |
Grade A, and why
first-plan-lens-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 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lens TypeScript / Node
Detecção fina
Pelo package.json + arquivos auxiliares:
| Sinal | Variante |
|---|---|
next.config.{js,ts,mjs} |
Next.js |
nest-cli.json ou @nestjs/* em deps |
NestJS |
vite.config.{js,ts} sem framework |
SPA Vite |
vite.config.{js,ts} + @sveltejs/kit |
SvelteKit |
astro.config.{js,ts,mjs} |
Astro |
remix.config.{js,ts} |
Remix |
@nuxt/kit ou nuxt.config.{js,ts} |
Nuxt |
expo em deps |
Expo (mobile) |
react-native em deps |
React Native bare |
electron em deps |
Electron |
bin field no package.json sem framework |
CLI Node |
express ou fastify em deps |
Backend tradicional |
pnpm-workspace.yaml |
Monorepo pnpm |
turbo.json |
Turborepo |
nx.json |
Nx |
Extração de padrões
Module system e tooling
"type": "module"no package.json -> ESMtsconfig.json-> verificarstrict,noImplicitAny,paths,target,module- Bundler: tsx / tsc / esbuild / swc / vite / webpack / rollup
- Runtime: Node, Bun, Deno
Validação de schemas
zodem deps -> Zodyupem deps -> Yupio-ts-> io-tsclass-validator+class-transformer-> nestjs-stylevalibot,arktype-> opções modernasjoi-> Joi (legacy)
Verificar onde validação acontece (boundary handlers? service layer?)
Async patterns
- Promises com
.then/.catchouasync/await? RxJSem deps -> reactive style (comum em Angular/NestJS)Effectlibrary?
Error handling
- Try/catch tradicional
Result<T, E>library (neverthrow,effect)- HTTP errors customizados (extends Error)
- Sentry / NewRelic / observability vendor em deps
Testing
vitest,jest,mocha,ava,tap?- Test runner config (
vitest.config.ts,jest.config.js) - Coverage tool (c8, nyc)
- E2E (
playwright,cypress,webdriverio)? - Mocks:
vi.mock,jest.mock,sinon,nock(HTTP)?
Frontend específico (se Next/Remix/Vite/etc)
- Sistema de design (Tailwind / CSS Modules / styled-components / emotion / vanilla-extract)
- State (
zustand,redux,jotai,recoil,pinia,mobx, Context apenas) - Data fetching (
@tanstack/react-query,swr,apollo,urql, server components) - Forms (
react-hook-form,formik,superforms) - Roteamento (App Router vs Pages Router em Next; file-based em Astro)
- i18n (
next-intl,i18next)
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 · 122 lines · 59 tokens per session scan A 44c07a9fa1b7
first-plan-lens-typescript is a skill published in the GitHub repository vynazevedo/first-plan (23 stars, last pushed 13d ago), licensed MIT. It adds 59 tokens to every session and 1,173 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-30.
Other skills, from other repositories
powerbi-custom-visuals
Power BI custom visual (.pbiviz) development with the pbiviz toolchain and its MCP server. Automatically invoke when the user mentions "custom visual", "pbiviz", "develop a Power BI visual", "powerbi-visuals-tools", "IVisual", "capabilities.json", "visual formatting model", "visual certification", "publish a visual to…
Draculabo__AntigravityManager
Replace runtime typeof checks and ad-hoc empty-string checks with lodash-es predicates.
typescript_mastery
Curated Knowledge API for AI Agents — 68 MCP tools, 200+ skill packs, 46K chunks, semantic search over 670K vectors, 5-layer validation pipeline. Works with Claude Code, Cursor, Cline, Windsurf.
cline-sdk
Comprehensive Cline SDK skill for building AI agents. Covers the Agent runtime, ClineCore sessions, custom tools, plugins, events, LLM providers, scheduling, multi-agent teams, and production deployment. Use for any task involving @cline/sdk or its sub-packages.
typescript-expert
TypeScript and JavaScript expert with deep knowledge of type-level programming, performance optimization, monorepo management, migration strategies, and modern tooling.
coding-standards
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.