obsigna typescript.instructions.md

TypeScript code-review instructions for a project that creates cryptographically signed audit records of AI-agent actions. They define import, typing, dependency, export, testing, and formatting rules.

In plain words
What is it for?
Use them when reviewing the TypeScript SDK, including imports, type safety, dependencies, exports, colocated tests, and code formatting.
Why use it?
They give reviewers a consistent way to catch TypeScript-specific errors and changes that could weaken the project's design constraints.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/agent-receipts/obsigna/typescript
Clone the repo
git clone --depth 1 https://github.com/agent-receipts/obsigna

Made for: GitHub Copilot.

Per session 163 This file is loaded in full into every session.
When invoked 163 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00163 $0.00163
Opus 5 $0.00081 $0.00081
Sonnet 5 $0.00033 $0.00033
Haiku 4.5 $0.00016 $0.00016

Measured yesterday against content hash d10a746f936c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

obsigna 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 yesterday.

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.

.github/instructions/typescript.instructions.md · 14 lines

What it actually says

TypeScript SDK review guidelines

  • ESM-only: relative imports must use .js extensions. Flag relative imports missing the .js extension (package imports and node: built-ins are fine).
  • Strict TypeScript: no any, no type assertions unless unavoidable. Flag as casts and any types.
  • Use import type for type-only imports (verbatimModuleSyntax is enabled).
  • Zero runtime dependencies — only node:crypto and node:sqlite. Flag any new dependency additions.
  • No default exports. Flag export default.
  • Colocated tests: foo.tsfoo.test.ts in the same directory.
  • Biome for formatting (tab indentation, double quotes).
Changes

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.

  1. yesterday First seen · 14 lines · 163 tokens per session scan A d10a746f936c

Subscribe to this mod's changes

obsigna typescript.instructions.md is an instructions file published in the GitHub repository agent-receipts/obsigna (20 stars, last pushed 2d ago), licensed Apache-2.0. It adds 163 tokens to every session, about $0.0008 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-30.