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/yunbow/ai-dev-os-rules-typescript/type-checknpx skills add yunbow/ai-dev-os-rules-typescript --skill type-checkgit clone --depth 1 https://github.com/yunbow/ai-dev-os-rules-typescriptWrote 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/yunbow/ai-dev-os-rules-typescript/type-check)<a href="https://agentmods.dev/skills/yunbow/ai-dev-os-rules-typescript/type-check"><img src="https://agentmods.dev/badge/skills/yunbow/ai-dev-os-rules-typescript/type-check.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.00028 | $0.00656 |
| Opus 5 | $0.00014 | $0.00328 |
| Sonnet 5 | $0.00006 | $0.00131 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
type-check 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Type & Lint Check Skill
A skill that runs TypeScript type checking and ESLint to detect and fix errors.
When to Execute
- For quality assurance after implementation is complete
- When requested with "type check", "lint", "type-check", etc.
- For final verification before committing
Execution Steps
1. TypeScript Type Check
npx tsc --noEmit
2. ESLint Check
npm run lint
3. Error Analysis
When errors occur, collect the following information:
- File path and line number
- Error code (TS2345, @typescript-eslint/no-explicit-any, etc.)
- Error message
4. Common Errors and Fixes
TypeScript Errors
| Error | Cause | Fix |
|---|---|---|
| TS2345 | Type mismatch | Convert to correct type or use assertion |
| TS2322 | Type error on assignment | Fix the type definition |
| TS7006 | Implicit any | Add explicit type annotation |
| TS2339 | Non-existent property | Review and fix the type definition |
| TS2304 | Undefined name | Add import or definition |
ESLint Errors
| Rule | Fix |
|---|---|
| @typescript-eslint/no-explicit-any | Change to unknown |
| @typescript-eslint/no-unused-vars | Remove or use the variable |
| react-hooks/exhaustive-deps | Fix the dependency array |
| @next/next/no-img-element | Use the <Image> component |
| import/order | Fix import order |
5. Run Auto-Fix (If Needed)
npm run lint:fix
npx prettier --write "src/**/*.{ts,tsx}"
6. Re-Check After Fixes
npx tsc --noEmit && npm run lint
Output Format
## Type & Lint Check Results
### TypeScript
- **Status**: ✅ No errors / ❌ X error(s)
### ESLint
- **Status**: ✅ No errors / ❌ X error(s)
### Error Details (If Any)
| File | Line | Error | Suggested Fix |
|------|------|-------|---------------|
| src/xxx.ts | 25 | TS2345: Type mismatch | Change `string` to `number` |
| src/yyy.tsx | 10 | no-explicit-any | Change `any` to `unknown` |
Status Symbols
- ✅ Check passed
- ⚠️ Warnings present (fix recommended)
- ❌ Errors present (must fix)
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 · 104 lines · 28 tokens per session scan A bdfae6748701
type-check is a skill published in the GitHub repository yunbow/ai-dev-os-rules-typescript (2 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 656 once invoked, about $0.0001 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
ai-dev-os-ticket
Creates a ticket (local file or GitHub Issue) containing an implementation summary and guideline checklist candidates. Analyzes the request the same way as /ai-dev-os-plan but outputs a ticket instead of executing the implementation. The ticket output destination follows the project's Ticket Settings in CLAUDE.md.
ai-dev-os-check
Checks code changes against AI Dev OS guidelines and automatically fixes violations. Based on benchmark Test 011: check+fix achieves +9.9 improvement vs report-only (+0.8). Supports git diff (default), branch comparison, and staged changes. Use --dry-run for report-only mode (no fixes applied).
ai-dev-os-plan
Creates an implementation plan with relevant AI Dev OS guideline checklists before writing any code. Analyzes the request, identifies affected files and applicable guidelines, then presents a plan with embedded checklist for user approval. Implementation begins only after approval.
ai-dev-os-scan
Scans ALL source files in the project against AI Dev OS guidelines. Unlike /ai-dev-os-check (which only checks git diff), this performs a full project-wide compliance scan. Use for initial audits, periodic full reviews, or after introducing new guidelines.
ai-dev-os-init
AI Dev OS initial setup wizard. Asks about the project's tech stack and scale, then generates an optimal 4-layer structure from templates. Used when starting a new project or introducing AI Dev OS.
ai-dev-os-review
Performs a comprehensive self-review before creating a PR. Combines guideline compliance checking (L3) with design-level review (L2) and philosophical alignment (L1). Unlike /ai-dev-os-check which only checks rules, this also evaluates architecture decisions and code design quality.