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/narpatsinghpurohit/tstack/adding-shared-schemasnpx skills add narpatsinghpurohit/tstack --skill adding-shared-schemasgit clone --depth 1 https://github.com/narpatsinghpurohit/tstackWrote 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/narpatsinghpurohit/tstack/adding-shared-schemas)<a href="https://agentmods.dev/skills/narpatsinghpurohit/tstack/adding-shared-schemas"><img src="https://agentmods.dev/badge/skills/narpatsinghpurohit/tstack/adding-shared-schemas.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.00079 | $0.00445 |
| Opus 5 | $0.00039 | $0.00222 |
| Sonnet 5 | $0.00016 | $0.00089 |
| Haiku 4.5 | $0.00008 | $0.00044 |
Grade A, and why
adding-shared-schemas 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 4d 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.
What it actually says
Task
Create shared schema: $ARGUMENTS
Adding Shared Schemas
Workflow
- [ ] Step 1: Create Zod schema file in packages/shared
- [ ] Step 2: Infer TypeScript types
- [ ] Step 3: Export from package index
- [ ] Step 4: Consume in NestJS (apps/api)
- [ ] Step 5: Consume in React (apps/web)
Schema patterns
z.coerce.number()for query params (strings from URL auto-coerced).default()for fields with sensible defaults.partial()to generate update DTOs from create DTOs.extend()to add server-generated fields to response schemas.pick()/.omit()to create subset schemas
Conventions
- One file per entity:
<entity>.schema.ts - Schema names:
create<Entity>Schema,update<Entity>Schema,<entity>ResponseSchema - Type names:
Create<Entity>Dto,Update<Entity>Dto,<Entity>Response - Always export both schema and inferred type
- No circular imports between schema files
Rules
- rules/schema-rules.md — Schema conventions
Examples
- examples/generic-schema.md — Generic schema template (Product)
- examples/course-schema.md — Real-world reference (exam-ai-guru)
References
- references/export-pattern.md — Schema file structure and export conventions
What ships with it
3 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.
- 4d ago First seen · 53 lines · 79 tokens per session scan A ae716bb15ff0
adding-shared-schemas is a skill published in the GitHub repository narpatsinghpurohit/tstack (5 stars, last pushed 5mo ago), licensed MIT. It adds 79 tokens to every session and 445 once invoked, about $0.0004 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…