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-api-endpointsnpx skills add narpatsinghpurohit/tstack --skill adding-api-endpointsgit clone --depth 1 https://github.com/narpatsinghpurohit/tstackWhat 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.00457 |
| Opus 5 | $0.00039 | $0.00229 |
| Sonnet 5 | $0.00016 | $0.00091 |
| Haiku 4.5 | $0.00008 | $0.00046 |
Grade A, and why
adding-api-endpoints 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.
What it actually says
Live Context
- Existing modules: !
ls apps/api/src/modules/ - Existing features: !
ls apps/web/src/features/
Task
Add API endpoint: $ARGUMENTS
Adding API Endpoints (Full-Stack)
Workflow
- [ ] Step 1: Define Zod schema in packages/shared
- [ ] Step 2: Add or confirm permission coverage
- [ ] Step 3: Add repository method in apps/api
- [ ] Step 4: Add service method in apps/api
- [ ] Step 5: Add controller endpoint with Swagger
- [ ] Step 6: Create TanStack Query hook in apps/web
- [ ] Step 7: Create React component consuming the hook
Conventions
- Permissions: Follow the
permission-guidelinesskill - Query keys:
[resource]for lists,[resource, id]for single items - Mutations: Always
invalidateQuerieson success - API client: Centralized Axios instance at
apps/web/src/lib/api-client.ts - Response envelope: Backend wraps in
{ data, status, message }. Accessr.data.datain hooks.
Examples
- examples/generic-endpoint.md — Generic CRUD endpoint template (Product)
- examples/crud-endpoint.md — Real-world reference (exam-ai-guru)
References
- references/query-patterns.md — Advanced TanStack Query usage
- references/swagger-patterns.md — Swagger decorator reference
What ships with it
4 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.
- 2d ago First seen · 48 lines · 79 tokens per session scan A c245109c626c
adding-api-endpoints 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 457 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
frontend-patterns
Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices. Use when building or reviewing React or Next.js components, state, or render performance.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
row-selection
Maintain rowSelection ID state with stable getRowId, single, multi, subrow, and Shift-range rules, selected row models, handler anchors, and manual-pagination semantics. Load when implementing getToggleSelectedHandler, enableRowRangeSelection, selectChildren, deselectParents, or selected IDs that outlive loaded Row…
material-ui-styling
Chooses the right Material UI styling approach (sx, styled, theme overrides, global CSS) from official MUI guidance. Use when styling @mui/material components, customizing themes, overriding slots, or comparing sx vs styled.
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
extract-errors
Use when adding new error messages to React, or seeing "unknown error code" warnings.