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/youdotcom-oss/dx-toolkit/agents-mdgit clone --depth 1 https://github.com/youdotcom-oss/dx-toolkitWrote 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/youdotcom-oss/dx-toolkit/agents-md)<a href="https://agentmods.dev/instructions/youdotcom-oss/dx-toolkit/agents-md"><img src="https://agentmods.dev/badge/instructions/youdotcom-oss/dx-toolkit/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 | $0.01314 | $0.01314 |
| Opus 5 | $0.00657 | $0.00657 |
| Sonnet 5 | $0.00263 | $0.00263 |
| Haiku 4.5 | $0.00131 | $0.00131 |
Grade A, and why
dx-toolkit 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 3d 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You.com DX Toolkit
Bun workspace for You.com developer packages and integrations.
Prefer the root README.md for user-facing setup. This file is for maintainers and coding agents working inside the repo.
Behavioral Guidelines
Think Before Coding
State assumptions. Surface tradeoffs. If multiple interpretations exist, present them instead of picking silently. If the repo already answers the question, use the codebase as the source of truth.
Simplicity First
Make the smallest change that solves the request. Do not add abstractions, fallbacks, or cleanup outside the task unless the change requires them.
Surgical Changes
Touch only the files the task needs. Match existing style. Remove imports or variables you orphan, but leave unrelated code alone.
Goal-Driven Execution
Turn work into verifiable outcomes. For behavior-changing feature or fix work,
use the tdd skill and work in red-green-refactor slices. For docs-only or
instruction-only edits, targeted doc validation is enough.
Validate Before Handoff
Run the narrowest checks that prove the change. If you skip executable tests,
say why. Before trusting repo docs, verify the current state with rg, find,
git log, or the relevant workflow/package files.
Repo Shape
Core Paths
| Path | Purpose |
|---|---|
.agents/skills/ |
Canonical skill directory for this repo |
packages/ |
Publishable packages |
.github/workflows/ |
CI, review, publish, and security workflows |
scripts/ |
Repo utilities and validation scripts |
docs/ |
Supporting docs such as performance notes |
Current Packages
packages/clipackages/mcppackages/ai-sdk-pluginpackages/langchain
Skill Surface
Prefer .agents/skills/ as the canonical agent workflow surface. Current
shared skills:
grill-mefor stress-testing plans or designsoptimize-agents-mdfor tightening repo instructionsreview-guidelinesfor code review conventionstddfor behavior-changing feature and fix worktypescript-lspfor type-aware TypeScript symbol exploration
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.
- 3d ago First seen · 203 lines · 1,314 tokens per session scan A a93e6426c400
dx-toolkit AGENTS.md is an instructions file published in the GitHub repository youdotcom-oss/dx-toolkit (25 stars, last pushed 13d ago), licensed MIT. It adds 1,314 tokens to every session, about $0.0066 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
openrouter-mcp-multimodal AGENTS.md
Instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
Plonk AGENTS.md
Instructions for ostapondo/Plonk, covering agent rules, layout, adding a module, build & verify and code style.
mcp-dockhand copilot-review.instructions.md
Instructions for strausmann/mcp-dockhand: When reviewing pull requests in this repository.
cyxj-groksearch CLAUDE.md
Instructions for chenyuxiaojin/cyxj-groksearch, covering claude.md, 常用命令 and 结构与坑.
minecraft-dev-mcp AGENTS.md
Instructions for MCDxAI/minecraft-dev-mcp, covering agent handbook – minecraft dev mcp, project snapshot, what agents should prioritize, architecture wayfinder (src/) and available mcp tools (for llm surfaces).
bray AGENTS.md
AGENTS.md instructions for forgesworn/bray, covering agents.md — nostr-bray, what this is, build & test, architecture and tool groups.