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/mort-lab/excel-mcp/prp-ts-executegit 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/prp-ts-execute)<a href="https://agentmods.dev/commands/mort-lab/excel-mcp/prp-ts-execute"><img src="https://agentmods.dev/badge/commands/mort-lab/excel-mcp/prp-ts-execute.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.00791 |
| Opus 5 | $0.00000 | $0.00396 |
| Sonnet 5 | $0.00000 | $0.00158 |
| Haiku 4.5 | $0.00000 | $0.00079 |
Grade A, and why
prp-ts-execute 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 4d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute TypeScript PRP
PRP File: $ARGUMENTS
Mission: One-Pass TypeScript Implementation Success
PRPs enable working TypeScript/React code on the first attempt through:
- Context Completeness: Everything needed, nothing guessed
- Progressive Validation: 4-level gates catch errors early
- Pattern Consistency: Follow existing TypeScript/React codebase approaches
- Type Safety: Leverage TypeScript's compile-time error detection
- Read PRPs/README.md to understand PRP concepts
Your Goal: Transform the PRP into working TypeScript code that passes all validation gates and maintains type safety.
Execution Process
-
Load PRP
- Read the specified TypeScript PRP file completely
- Absorb all context, patterns, requirements and gather codebase intelligence
- Use the provided documentation references and file patterns, consume the right documentation before the appropriate todo/task
- Trust the PRP's context and guidance - it's designed for one-pass success
- If needed do additional codebase exploration and research as needed
- Pay special attention to TypeScript interfaces, component patterns, and Next.js App Router structure
-
ULTRATHINK & Plan
- Create comprehensive implementation plan following the PRP's task order
- Break down into clear todos using TodoWrite tool
- Use subagents for parallel work when beneficial (always create prp inspired prompts for subagents when used)
- Follow the TypeScript/React patterns referenced in the PRP
- Use specific file paths, interface names, component names, and type definitions from PRP context
- Never guess - always verify the codebase patterns and examples referenced in the PRP yourself
- Consider TypeScript compilation dependencies (types before components, components before pages)
-
Execute Implementation
- Follow the PRP's Implementation Tasks sequence, add more detail as needed, especially when using subagents
- Use the TypeScript/React patterns and examples referenced in the PRP
- Create files in locations specified by the desired codebase tree
- Apply TypeScript naming conventions from the task specifications and CLAUDE.md
- Ensure proper TypeScript typing throughout (interfaces, props, return types)
- Follow Next.js App Router patterns for file-based routing
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.
- 4d ago First seen · 66 lines · 0 tokens per session scan A 72391be95f86
prp-ts-execute is a command published in the GitHub repository mort-lab/excel-mcp (5 stars, last pushed 26d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 791 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
typegen
Run Sanity TypeGen and troubleshoot type generation issues.
zooza-setup
One-time Zooza setup — teaches Claude your business vocabulary so it understands your terms in every future session.
example-command
TODO — one-line description shown in the slash-command picker.
status
Show current session collaboration status including active sessions, claims, and your session info.
end
End the current collaboration session and release all claims.
generate-idl-client
Generate TypeScript client from Solana program IDL using Codama or Anchor.