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.
git clone --depth 1 https://github.com/yu-iskw/skill-inspectorWrote 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/rules/yu-iskw/skill-inspector/typescript-coding-convention)<a href="https://agentmods.dev/rules/yu-iskw/skill-inspector/typescript-coding-convention"><img src="https://agentmods.dev/badge/rules/yu-iskw/skill-inspector/typescript-coding-convention/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/yu-iskw/skill-inspector/typescript-coding-convention"><img src="https://agentmods.dev/badge/rules/yu-iskw/skill-inspector/typescript-coding-convention.svg" alt="Reviewed on agentmods" width="80" 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.03499 | $0.03499 |
| Opus 5.5 | $0.01400 | $0.01400 |
| Sonnet 5.5 | $0.00700 | $0.00700 |
| Haiku 4.5 | $0.00350 | $0.00350 |
Grade A, and why
typescript-coding-convention 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 1mo 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.
This is a copy
98% identical to typescript-coding-convention — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript Style Guide
This guide outlines the default-standard coding conventions for TypeScript, based on the Google TypeScript Style Guide, supplemented with best practices from other widely-used TypeScript style guides.
1. Syntax
1.1. Identifiers
Identifiers must use only ASCII letters, digits, underscores (for constants and structured test method names), and the '$' sign.
| Style | Category |
|---|---|
UpperCamelCase |
class / interface / type / enum / decorator / type / parameters |
lowerCamelCase |
variable / parameter / function / method / property / module alias |
CONSTANT_CASE |
global constant values, including enum values |
- Abbreviations: Treat abbreviations like acronyms as whole words (e.g.,
loadHttpUrl, notloadHTTPURL). - Dollar sign: Avoid using
$in identifiers, except when aligning with third-party framework conventions (e.g.,jquery). - Type parameters: May use a single upper case character (
T) orUpperCamelCase. - Test names: Test method names may be structured with
_separators (e.g.,testX_whenY_doesZ()). _prefix/suffix: Do not use_as a prefix or suffix, or as an identifier by itself.
1.2. Aliases
When aliasing an existing symbol, use the format of the existing identifier. For variables, use const, and for class fields, use readonly.
1.3. Naming Style
Names should not be decorated with information already included in the type.
- Do not use trailing or leading underscores for private properties or methods.
- Do not use the
opt_prefix for optional parameters. - Do not prefix interfaces with
I(e.g.,IUsershould beUser). - Prefix booleans with
isorhasfor clarity (e.g.,isLoggedIn,hasPermission).
1.4. File Encoding
For non-ASCII characters, use the actual Unicode character (e.g., ∞). For non-printable characters, the equivalent hex or Unicode escapes (e.g., \u221e) can be used along with an explanatory comment.
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.
- 1mo ago First seen · 281 lines · 3,499 tokens per session scan A 7a3ad22d8a9c
typescript-coding-convention is a cursor rule published in the GitHub repository yu-iskw/skill-inspector (2 stars, last pushed 20d ago), licensed Apache-2.0. It adds 3,499 tokens to every session, about $0.0140 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 98% identical to typescript-coding-convention, differing in 6 lines, and is treated as a copy.
Other cursor rules, from other repositories
vue-typescript-patterns
A set of coding rules for Vue 3 projects using TypeScript, a language that adds type checking to JavaScript. It covers component structure, file locations, TypeScript usage, and Pinia, a library for shared application state.
nextjs-typescript-app-cursorrules-prompt-file
Cursor rules for Next.js development with TypeScript integration.
agent-autonomy
AI agent autonomy threat agent — detects excessive autonomy, goal misalignment, unconstrained action scope, missing human-in-the-loop checkpoints, cascading multi-agent failures, and autonomous resource consumption against Processes.
ts
A set of TypeScript coding rules covering types, naming, file organization, error handling, and strict type checking. TypeScript is JavaScript with checks that help catch many mistakes before the program runs.
naming-conventions-rule
A small set of naming rules for TypeScript, Node.js, and Next.js projects. It defines how directories and React components should be named and exported.
typescript-security
A secret scanner owns hardcoded keys. Read secrets from the environment and fail startup when a required one is missing.