Borrowing it
Nothing to install: this file belongs to mort-lab/excel-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mort-lab/excel-mcp/main/.claude/commands/typescript/TS-review-staged-unstaged.mdgit clone --depth 1 https://github.com/mort-lab/excel-mcpWrote 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/mort-lab/excel-mcp/ts-review-staged-unstaged)<a href="https://agentmods.dev/commands/mort-lab/excel-mcp/ts-review-staged-unstaged"><img src="https://agentmods.dev/badge/commands/mort-lab/excel-mcp/ts-review-staged-unstaged/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/commands/mort-lab/excel-mcp/ts-review-staged-unstaged"><img src="https://agentmods.dev/badge/commands/mort-lab/excel-mcp/ts-review-staged-unstaged.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.00000 | $0.00891 |
| Opus 5 | $0.00000 | $0.00445 |
| Sonnet 5 | $0.00000 | $0.00178 |
| Haiku 4.5 | $0.00000 | $0.00089 |
Grade A, and why
TS-review-staged-unstaged 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 12d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
List and review any files in the staging area, both staged and unstaged. Ensure you look at both new files and modified files.
Check the diff of each file to see what has changed.
Previous review report: $ARGUMENTS
May or may not be added, ignore the previous review if not specified.
Review Focus Areas
-
TypeScript Code Quality
- Strict TypeScript usage with explicit types
- No
anytypes - useunknownif type is truly unknown - Proper type imports with
import type { }syntax - Component props interfaces defined
- Astro's built-in types used (HTMLAttributes, ComponentProps)
- Following TypeScript strict mode compliance
-
Astro-Specific Patterns
- Proper hydration directives usage (client:load, client:visible, client:idle)
- Static-first approach with selective hydration
- Astro components for static content, framework components only for interactivity
- Proper use of Astro.props and component interfaces
- Content collections with Zod schemas
- Server islands implementation where appropriate
-
Performance & Bundle Optimization
- No unnecessary client-side JavaScript
- Appropriate hydration strategy choices
- Image optimization with Astro's Image component
- Bundle size considerations
- No over-hydration of static content
-
Security & Validation
- Input validation with Zod schemas
- Environment variables properly typed with astro:env
- Content Security Policy implementation
- No hardcoded secrets in client-side code
- API route validation with proper error handling
-
Content Management
- Content collections properly configured
- Zod schemas for all content types
- Type-safe content queries
- Proper content rendering and data handling
-
Package Management
- Using pnpm (not npm or yarn)
- Proper dependency management
- No unused dependencies
- Correct dev vs runtime dependencies
-
Code Structure & Architecture
- Components under 200 lines (500 line hard limit)
- Functions under 50 lines with single responsibility
- Proper separation of concerns
- Feature-based organization
- Islands architecture principles followed
-
Testing & Quality Assurance
- Vitest configuration and tests
- 80%+ test coverage maintained
- Component tests using Astro Container API
- API route integration tests
- Proper mocking of external dependencies
-
Build & Development
astro checkpasses with zero errors- ESLint compliance with zero warnings
- Prettier formatting applied
- Production build succeeds
- No hydration mismatches
-
Documentation & Maintenance
- Clear component interfaces
- Proper prop descriptions
- CLAUDE.md updates for new patterns/dependencies
- README updates if needed
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.
- 12d ago First seen · 127 lines · 0 tokens per session scan A 7a7f21ebd658
TS-review-staged-unstaged is a command published in the GitHub repository mort-lab/excel-mcp (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 891 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
devkit.typescript.code-review
Provides comprehensive TypeScript monorepo code review for Nx workspaces including NestJS backend, React web, and React Native mobile apps. Use when reviewing architecture, boundaries, security, performance, CI/CD and Nx-specific practices.
typegen
Run Sanity TypeGen and troubleshoot type generation issues.
harness:naming-craft
LLM-judgment skill that critiques identifier names (variables, functions, types, files) against a curated rubric catalog seeded from Martin / Beck / Karlton. First craft-pipeline ceiling skill; cross-cutting (other craft skills call into it for domain-specific naming).
review
Comprehensive code review for blz changes.
stats
Show squad-mcp observability dashboard for past runs in this workspace. Bar charts, score distribution, verdict mix, sparkline trend, per-agent token + wall-clock cost breakdown. Reads .squad/runs.jsonl; never writes. Triggers: "squad stats", "run history", "score distribution", "where did the tokens go", "how much…
mdd-rules-typescript
Rules loaded when stack.language includes typescript. Applied additively to audit criteria and build checklists.