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/generate-bionpx skills add phazonoverload/devadvokit --skill generate-biogit 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.00045 | $0.00954 |
| Opus 5 | $0.00023 | $0.00477 |
| Sonnet 5 | $0.00009 | $0.00191 |
| Haiku 4.5 | $0.00005 | $0.00095 |
Grade A, and why
generate-bio 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Before doing anything else:
- Check if
~/.devadvokit.mdexists. - If it does, read it silently and use it throughout this skill.
- If it does not, stop and tell the user: "I need your DevRel context before I can run this skill. Please run /setup-devadvokit first."
Q&A
Ask these questions one at a time. Wait for each answer before asking the next.
-
What's this bio for? (e.g. conference speaker profile, LinkedIn about section, company team page, personal website, podcast guest intro, book jacket — be specific if you can)
-
How long should it be? Choose one:
- One-liner — a single sentence (~20–30 words)
- Short — one tight paragraph (~50–75 words)
- Medium — two paragraphs (~100–150 words)
- Long — three or more paragraphs (~200–300 words) — or give a specific word count or character limit if the platform requires one.
-
First person ("I'm a developer advocate...") or third person ("Jane is a developer advocate...")?
-
On a scale of 1 to 5, how much should this bio focus on your current employer?
- 1 — employer-led: opens with your company, leads with what you do there, frames your expertise through your current role. Suits company team pages, sponsored content, and employer-brand contexts.
- 3 — balanced: current role is present and clear, but career-wide expertise and your broader identity carry equal weight. Suits most conference and speaker bios.
- 5 — employer-light: current role is mentioned but not the focus. Leads with career-wide expertise, personal brand, and what you're known for across the industry. Suits personal sites, independent speaking, and contexts where you want to be seen as more than your current job.
Answer with a number. If unsure, 3 is a safe default for most conference bios.
Generating the bio
Use the answers to the Q&A and the context from ~/.devadvokit.md to produce the bio. Apply the scale as follows:
Scale 1: Open with the company and current role. Frame expertise in terms of what the speaker does at this employer. Previous roles and career-wide specialisms appear only if space allows, and only in support of the current role. Location and hobbies may appear if the format and length suit it, but the employer is the primary anchor.
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 · 69 lines · 45 tokens per session scan A 0a8f31284027
generate-bio is a skill published in the GitHub repository phazonoverload/devadvokit (16 stars, last pushed 4mo ago), licensed MIT. It adds 45 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
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…