Borrowing it
Nothing to install: this file belongs to mhaviv/pr-narrator-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/mhaviv/pr-narrator-mcp/main/.github/instructions/typescript.instructions.mdgit clone --depth 1 https://github.com/mhaviv/pr-narrator-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/instructions/mhaviv/pr-narrator-mcp/typescript)<a href="https://agentmods.dev/instructions/mhaviv/pr-narrator-mcp/typescript"><img src="https://agentmods.dev/badge/instructions/mhaviv/pr-narrator-mcp/typescript.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.1 | $0.01075 | $0.01075 |
| Opus 5 | $0.00537 | $0.00537 |
| Sonnet 5 | $0.00215 | $0.00215 |
| Haiku 4.5 | $0.00108 | $0.00108 |
Grade A, and why
pr-narrator-mcp typescript.instructions.md 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 6d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript Review Rules
Type Safety
- Strict null checks — no
!non-null assertions without a comment justifying why it is safe - All function parameters must be explicitly typed (no implicit
any) - Use
unknowninstead ofany— narrow with type guards - Flag
as anycasts — useas Record<string, unknown>or proper types instead - Async functions must have explicit
Promise<T>return types on public APIs - Use optional chaining (
?.) and nullish coalescing (??) over manual null checks
// Avoid
const name = obj && obj.user && obj.user.name;
// Prefer
const name = obj?.user?.name;
Zod Type Derivation
- Use
z.infer<typeof schema>for deriving types from Zod schemas — never duplicate types manually - Tool input types must always be derived from the tool's Zod schema
// Avoid: manual type that duplicates the Zod schema
interface MyInput {
repoPath?: string;
summary?: string;
}
// Prefer: derive from Zod
export const mySchema = z.object({
repoPath: z.string().optional().describe("Path to the git repository"),
summary: z.string().optional().describe("Summary text"),
});
export type MyInput = z.infer<typeof mySchema>;
Interface vs Type
- Use
interfacefor object shapes, especially tool result types - Use
typeonly for unions, intersections, or mapped types - Tool results must use
interfacewithResultsuffix
// Prefer: interface for result objects
export interface GenerateCommitMessageResult {
success: boolean;
title: string;
errors: string[];
}
// Acceptable: type for unions
type PrefixStyle = "capitalized" | "bracketed";
Error Handling in Tools
- Tool handlers must never throw — return structured error results
- Use try/catch internally and populate the
errorsarray
// Avoid: throwing in a tool handler
export async function myTool(input: MyInput, config: Config) {
const data = getSomething();
if (!data) throw new Error("Not found");
return data;
}
// Prefer: return structured error
export async function myTool(input: MyInput, config: Config): Promise<MyResult> {
const data = getSomething();
if (!data) {
return { success: false, errors: ["Not found"], data: null };
}
return { success: true, data, errors: [] };
}
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.
- 6d ago First seen · 150 lines · 1,075 tokens per session scan A edf0283db388
pr-narrator-mcp typescript.instructions.md is an instructions file published in the GitHub repository mhaviv/pr-narrator-mcp (1 stars, last pushed 6mo ago), licensed MIT. It adds 1,075 tokens to every session, about $0.0054 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.