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 instructions/fjlaubscher/depot/agents-mdgit clone --depth 1 https://github.com/fjlaubscher/depotWrote 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/fjlaubscher/depot/agents-md)<a href="https://agentmods.dev/instructions/fjlaubscher/depot/agents-md"><img src="https://agentmods.dev/badge/instructions/fjlaubscher/depot/agents-md.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.01212 | $0.01212 |
| Opus 5 | $0.00606 | $0.00606 |
| Sonnet 5 | $0.00242 | $0.00242 |
| Haiku 4.5 | $0.00121 | $0.00121 |
Grade A, and why
depot 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 5d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for working in the depot monorepo (pnpm workspace with core, CLI, and web packages).
Workspace Layout
| Package | Path | Purpose |
|---|---|---|
@depot/core |
packages/core |
Type definitions + shared utilities (single source of truth) |
@depot/cli |
packages/cli |
Fetches Wahapedia CSV exports and emits cleaned JSON |
@depot/web |
packages/web |
React PWA that ships the experience + offline cache |
| Scripts | scripts/*.mjs |
Supporting utilities (e.g., data copy helper) |
Common Commands
pnpm install- install workspace dependenciespnpm start- build core + cli, generate data, copy assets, start web dev serverpnpm dev- start web dev server only (requires data already inpackages/web/public/data)pnpm --filter @depot/cli start- generate fresh data (downloads + converts)pnpm refresh-data- regenerate data and force a re-downloadpnpm regen-data- regenerate data from the cached CSVs inpackages/cli/dist/source_data(no network)pnpm build- production build: build packages, regenerate data, copy assetspnpm format/pnpm lint/pnpm typecheck/pnpm test- quality gates (run before commits)pnpm clean- clean all package outputs
Data + Build Flow
- CLI fetches CSV from Wahapedia URLs at
https://wahapedia.ru/wh40k11ed/{File}.csv, or reusespackages/cli/dist/source_datawhen every CSV is already cached there (so reruns work offline). - CSV is converted to JSON using
@depot/coretypes. - Output lands in
packages/cli/dist/data/. scripts/copy-data.mjscopiesdist/data/intopackages/web/public/data/.- The web app reads from
public/data/and caches in IndexedDB for offline use.
Scripts
scripts/copy-data.mjsdeletes the existingpackages/web/public/datadirectory, then copiespackages/cli/dist/datainto it. It runs automatically inpnpm startandpnpm build; manual runs are rarely needed.
Functions
- Cloudflare Pages Functions live under the root
functions/directory (currently just[[path]].ts, which injects og/meta tags for faction, datasheet and detachment routes). - Code there runs on the Pages runtime: rely on Web-standard APIs only (no Node built-ins).
- Local iteration:
pnpm dev:wranglerserves the built web app through the Pages runtime.
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.
- 5d ago First seen · 75 lines · 1,212 tokens per session scan A 2eefae2b2dfa
depot AGENTS.md is an instructions file published in the GitHub repository fjlaubscher/depot (11 stars, last pushed 13d ago), licensed MIT. It adds 1,212 tokens to every session, about $0.0061 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.
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).
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.
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.
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 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).