agentmods.dev

repotector CLAUDE.md

Repository-specific instructions for working with the Repotector project, a guarded codebase with tools that map the project and check changes. They describe the required order for starting, editing, and finishing work.

In plain words
What is it for?
Use them when adding code, editing files, checking the impact of changes, running quality checks, and ending an agent session in the Repotector repository.
Why use it?
They reduce the risk of changing the wrong code or breaking dependent parts of the repository. They also leave a handover summary for the next coding agent.

Instructions file

0 1mo ago A scan 217 tokens copy · 97% MIT
View the source file dir-ai/repotector
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/dir-ai/repotector/claude-md
Clone the repo
git clone --depth 1 https://github.com/dir-ai/repotector
Per session 217 This file is loaded in full into every session.
When invoked 217 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 97% copy Near-identical to another mod 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.00217 $0.00217
Opus 5 $0.00109 $0.00109
Sonnet 5 $0.00043 $0.00043
Haiku 4.5 $0.00022 $0.00022

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

Security

Grade A, and why

repotector CLAUDE.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.

Origin

This is a copy

97% identical to repotector copilot-instructions.md — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

CLAUDE.md · 13 lines

What it actually says

Project notes for Claude

⬡ Repotector — this repo is guarded (REPOTECTOR/2)

Before you touch anything:

  1. handshake({ who }) on the repotector MCP server — you are logged in and handed the map. No deep tool answers first.
  2. city_map() — intent, danger list, conventions, built-vs-missing. Read it before reading code.
  3. New code → find_existing(intent). Editing → blast_radius(files). Finishing → quality_gates() then depart({ summary }).

Rules: reuse before rebuilding · protect dependents · follow the repo canon · keep files small · your depart summary becomes the next agent’s briefing. No server connected? run npx repotector mcp. A repo with no .repotector/? propose npx repotector init.

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 · 13 lines · 217 tokens per session scan A 10a758fa1c25

Subscribe to this mod's changes

repotector CLAUDE.md is an instructions file published in the GitHub repository dir-ai/repotector (0 stars, last pushed 1mo ago), licensed MIT. It adds 217 tokens to every session, about $0.0011 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to repotector copilot-instructions.md, differing in 2 lines, and is treated as a copy.

Productivity
Related

Other instructions, from other repositories

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.

github/spec-kit · 7,104 tokens

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).

microsoft/vscode · 6,785 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens