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 skills/phazonoverload/devadvokit/setup-devadvokitnpx skills add phazonoverload/devadvokit --skill setup-devadvokitgit 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.00043 | $0.00954 |
| Opus 5 | $0.00022 | $0.00477 |
| Sonnet 5 | $0.00009 | $0.00191 |
| Haiku 4.5 | $0.00004 | $0.00095 |
Grade A, and why
setup-devadvokit 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run an interactive setup to capture your DevRel context and content library. The output is written to ~/.devadvokit.md and read automatically by every other DevAdvokit skill.
If ~/.devadvokit.md already exists, do not overwrite it without asking first. Offer to update individual sections or append to the content library instead.
Part 1: Identity and context
Ask the following questions one at a time. Wait for the user's answer before asking the next question. Do not batch questions.
- What's your name?
- What's your current job title and company?
- In one sentence, what does your company do — in plain language, not marketing copy?
- What are your specialist areas in this role? (e.g. the technical domains you focus on, the audiences you work with, the type of work you spend most time on)
- How many years have you been working in Developer Relations?
- List your previous roles briefly, most recent first. For each: job title, company, and the specialist areas you focused on in that role.
- What are your broader specialist areas across your whole career? (Themes that run across roles, not just your current one)
- Who do you primarily write and speak for? Describe them: job title, seniority, what context they're in when they encounter your content.
- What platforms do you publish to? (e.g. company blog, personal blog, LinkedIn, X, YouTube, newsletter)
- What are your main content pillars or recurring talk topics?
- What's your writing voice like? (e.g. direct and technical, conversational, educational, opinionated)
- Are there any words, phrases, or styles you want to avoid in your content?
- Where are you based? (City, country, or region — whatever level of detail you're comfortable with)
- What do you do outside of work? (Hobbies, interests, side projects — anything you'd be happy to see appear in a bio)
If any answer is vague or very short, consult reference/devadvokit-md-schema.md for guidance on what a strong answer looks like and ask a follow-up question before moving on.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 98 lines · 43 tokens per session scan A 87df7b83fc79
setup-devadvokit is a skill published in the GitHub repository phazonoverload/devadvokit (16 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 954 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…