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 commands/hktitan/cursor-best-practices/generate-typesgit clone --depth 1 https://github.com/HKTITAN/cursor-best-practicesWrote 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/commands/hktitan/cursor-best-practices/generate-types)<a href="https://agentmods.dev/commands/hktitan/cursor-best-practices/generate-types"><img src="https://agentmods.dev/badge/commands/hktitan/cursor-best-practices/generate-types.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.00000 | $0.00443 |
| Opus 5 | $0.00000 | $0.00221 |
| Sonnet 5 | $0.00000 | $0.00089 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
generate-types 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 5d 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
Generate TypeScript types or type definitions from schemas, APIs, or data structures.
Steps
-
Identify source
- Check if I @-mentioned a file (OpenAPI spec, GraphQL schema, JSON schema, API response example).
- Or identify the source from context (API endpoint, schema file, etc.).
- Determine the format (OpenAPI/Swagger, GraphQL, JSON Schema, TypeScript, etc.).
-
Generate types
- Use appropriate tool or generate manually:
- OpenAPI/Swagger: Use
openapi-typescriptor similar - GraphQL: Use
graphql-codegenor similar - JSON Schema: Convert to TypeScript types
- API Response: Infer types from example JSON
- OpenAPI/Swagger: Use
- Generate types that match the project's style (interfaces vs types, naming conventions).
- Use appropriate tool or generate manually:
-
Place types appropriately
- Create or update type files in the project's types directory (e.g.
types/,@types/,src/types/). - Follow project conventions for type file organization.
- Use appropriate file naming (e.g.
api.types.ts,schema.types.ts).
- Create or update type files in the project's types directory (e.g.
-
Update imports
- If types are used elsewhere, update imports.
- Ensure type exports are correct.
- Check for any circular dependencies.
-
Verify types
- Check that generated types are valid TypeScript.
- Ensure types match the source schema/structure.
- Test that types work with existing code (if applicable).
-
Report
- What source was used (file, API, schema)
- Where types were generated (file path)
- What types were created (interfaces, types, enums)
- Any issues or warnings
Rules
- Apply project rules from
.cursor/rulesorAGENTS.mdwhen relevant (e.g. type naming, style preferences). - Generate types that are maintainable and well-documented.
- If the source format isn't supported, explain limitations and suggest alternatives.
- For API types, consider versioning and backward compatibility.
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.
- 5d ago First seen · 45 lines · 0 tokens per session scan A e9cd8f703667
generate-types is a command published in the GitHub repository HKTITAN/cursor-best-practices (5 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 443 tokens. 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 commands, from other repositories
react
Apply React with TypeScript best practices.
typescript
Apply TypeScript best practices and coding standards.
vue3
Apply Vue 3 with TypeScript and Composition API patterns.
newpkg
Generate new package with Nx.
tsc
Use the TypeScript compiler to check for type errors in your codebase.
handle-pr-comments
Fetch all PR comments, classify by severity, and present for user approval before acting.