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/phazonoverload/devadvokit/agents-mdgit clone --depth 1 https://github.com/phazonoverload/devadvokitWhat 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.01082 | $0.01082 |
| Opus 5 | $0.00541 | $0.00541 |
| Sonnet 5 | $0.00216 | $0.00216 |
| Haiku 4.5 | $0.00108 | $0.00108 |
Grade A, and why
devadvokit 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 2d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevAdvokit — Agent Guide
This repo contains AI agent skills for Developer Relations practitioners. Skills are installed via the npx skills CLI and run inside Claude Code or compatible agents.
What this is
DevAdvokit provides skills for DevRel practitioners:
/setup-devadvokit— one-time setup that writes your professional context to~/.devadvokit.md/generate-cfp— generates a complete conference proposal through a structured Q&A/generate-bio— generates a speaker or author bio with controls for length, person, and employer focus/build-talk-outline— turns a CFP submission into a timed outline with demo risk assessments and Patrick Winston principles applied throughout
All skills read ~/.devadvokit.md at runtime. If it's missing, they stop and redirect to /setup-devadvokit.
Repository structure
devadvokit/
├── skills/
│ ├── setup-devadvokit/
│ │ ├── SKILL.md
│ │ └── reference/
│ │ └── devadvokit-md-schema.md
│ ├── generate-cfp/
│ │ ├── SKILL.md
│ │ └── reference/
│ │ ├── cfp-evaluation-criteria.md
│ │ └── cfp-anti-patterns.md
│ ├── generate-bio/
│ │ ├── SKILL.md
│ │ └── reference/
│ │ └── bio-contexts.md
│ └── build-talk-outline/
│ ├── SKILL.md
│ └── reference/
│ ├── outline-structure-patterns.md
│ ├── demo-risk-patterns.md
│ └── winston-talk-principles.md
├── shared/
│ └── ai-antipatterns.md
├── AGENTS.md
├── README.md
├── LICENSE
└── .gitignore
No build step. The skills/ directory is the single source of truth and the install target. Edit files directly — what's in the repo is what gets installed.
Adding a new skill
- Create
skills/{name}/SKILL.mdwith the following frontmatter:
---
name: your-skill-name
description: One-sentence description of what the skill does.
---
Only name and description in frontmatter. Nothing else.
- Add a
reference/subdirectory inside the skill folder if you need supporting documents. Reference files are copied alongside the skill on install.
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.
- 2d ago First seen · 116 lines · 1,082 tokens per session scan A 069f07983376
devadvokit AGENTS.md is an instructions file published in the GitHub repository phazonoverload/devadvokit (16 stars, last pushed 4mo ago), licensed MIT. It adds 1,082 tokens to every session, about $0.0054 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
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.
buildNext
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
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, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit 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.
langchain 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.