difit is a command-line tool that starts a local web server showing Git commit differences in a GitHub-style file-change viewer. Developers use it to inspect and review local diffs or pull requests, with review comments that can also be copied into AI prompts. The catalogue entries connect coding-agent workflows to difit for requesting or performing reviews.
Borrowing it
Nothing to install: this file belongs to yoshiko-pg/difit. 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/yoshiko-pg/difit/main/AGENTS.mdgit clone --depth 1 https://github.com/yoshiko-pg/difitWrote 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/yoshiko-pg/difit/agents-md)<a href="https://agentmods.dev/instructions/yoshiko-pg/difit/agents-md"><img src="https://agentmods.dev/badge/instructions/yoshiko-pg/difit/agents-md/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/instructions/yoshiko-pg/difit/agents-md"><img src="https://agentmods.dev/badge/instructions/yoshiko-pg/difit/agents-md.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.00698 | $0.00698 |
| Opus 5.5 | $0.00279 | $0.00279 |
| Sonnet 5.5 | $0.00140 | $0.00140 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
difit AGENTS.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 2mo 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 — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
The TypeScript sources live under src, split by runtime: src/cli handles command parsing and Git integration, src/server hosts the Express diff service, src/client renders the React web UI, and shared helpers sit in src/utils and src/types. Unit and integration tests live next to the code they cover as *.test.ts or *.test.tsx, and fixtures under docs/ support screenshots and copy decks. Built artifacts land in dist/ after pnpm build; do not edit them manually. Static assets for the UI reside in public/, while automation scripts live in scripts/.
Build, Test, and Development Commands
pnpm install— install workspace dependencies (Node ≥21; usemiseto stay aligned).pnpm dev— run the local development loop (boots the CLI server and UI with hot reload).pnpm build— generate the CLI bundle and production web assets via TypeScript project references and Vite.pnpm test/pnpm test:watch— execute the Vitest suite once or in watch mode.pnpm check,pnpm check:fix, andpnpm format— apply oxlint type-aware checks and oxfmt formatting before you commit.
Coding Style & Naming Conventions
The codebase uses strict TypeScript (tsconfig.strictest) and 2-space indentation; avoid any and prefer explicit types. Import types with import type and keep module order consistent; oxlint enforces unused imports/variables and type-aware safety rules. React components live under src/client; use PascalCase filenames for components, kebab-case for utilities, and co-locate UI-specific helpers when practical. Run pnpm format before submitting to apply oxfmt formatting.
Testing Guidelines
Vitest with the happy-dom environment drives unit and integration coverage, and React work should lean on Testing Library helpers. Place new tests alongside the implementation using the name.test.ts[x] pattern and prefer descriptive describe blocks tied to features. Ensure asynchronous flows await their assertions and cover both CLI (src/cli) and server (src/server) branches when they change; use pnpm test --runInBand if watchers behave flakily in CI.
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.
- 2mo ago First seen · 30 lines · 698 tokens per session scan A 4ebdf879680d
difit AGENTS.md is an instructions file published in the GitHub repository yoshiko-pg/difit (3,296 stars, last pushed 2mo ago), licensed MIT. It adds 698 tokens to every session, about $0.0028 per session on Opus 5.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.
Other instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.