agentmods.dev

developer

A coding assistant for writing, reviewing, refactoring, and testing software in different programming languages. It selects guidance for the language involved in the task.

In plain words
What is it for?
Use it to create code, fix bugs, improve existing code, add tests, or review code quality.
Why use it?
It keeps language-specific coding advice focused and checks whether the project has a delivery pipeline before code changes begin.

Skill for Claude CodeCodex

2 3mo ago B scan 160 tokens original MIT
View the source file P47Phoenix/Claude-Plugins
Install

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.

agentmods
npx agentmods add skills/p47phoenix/claude-plugins/developer
Any agent
npx skills add P47Phoenix/Claude-Plugins --skill developer
Clone the repo
git clone --depth 1 https://github.com/P47Phoenix/Claude-Plugins

Made for: Claude Code, Codex.

Per session 160 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,639 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00160 $0.03639
Opus 5 $0.00080 $0.01819
Sonnet 5 $0.00032 $0.00728
Haiku 4.5 $0.00016 $0.00364

Measured yesterday against content hash 5e415cd683c0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

developer scanned grade B with 1 finding 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 yesterday.

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.

Asks the agent to reveal its instructionsmediumSystem prompt leakage

Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.

Skip language detection. Follow pre-flight and output instructions in the agent-prompt file.
delivery-team/skills/developer/SKILL.md · 300 lines

How it starts

The opening of the file, as written. The whole thing — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Developer Agent

Design Principle: Language Context Isolation

This skill intentionally keeps language-specific knowledge out of the main context window. When a coding task is requested, a sub-agent is spawned carrying only the single relevant language reference. This means:

  • A Python task loads only references/languages/python.md
  • A TypeScript task loads only references/languages/typescript.md
  • No other language files are loaded — ever

The main context receives only the finished code artifact. All language-specific reasoning happens inside the sub-agent's isolated context.

Pipeline Context Check

Before executing any write or fix task, check for delivery pipeline context:

  1. Check if .delivery/config.yml exists in the current working directory.
  2. If YES: proceed — this project has an active delivery pipeline configuration.
  3. If NO: announce a warning before proceeding:

WARNING: No delivery pipeline config found. This implementation is not going through the delivery-flow pipeline. QA evaluator-optimizer loop, DoD validation, and defect prevention will NOT run. Start the pipeline with delivery-team:delivery-flow first, or say "skip pipeline" to proceed without quality gates.

This check does NOT block implementation — it warns. Proceed for quick fixes or prototyping if the user explicitly confirms. The warning makes bypass visible and intentional, not silent.

Phase 1: Language Detection

Detect the target language from (in priority order):

  1. File extension in context — see the Language → Reference File Mapping table below for all supported extensions
  2. Imports or syntax in pasted code
  3. User's explicit statement
  4. File being edited in the current session

If language is ambiguous, ask before proceeding. Do not assume.

Declare before every task:

Language: [LANG] | Task: [write / fix / refactor / review / test / explain / coding-standards] | Reference: references/languages/<lang>.md | Clean Code: [default | <custom-path>]

Read the full file on GitHub · 300 lines

Files

What ships with it

26 files 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.

Changes

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.

  1. yesterday First seen · 300 lines · 160 tokens per session scan B 5e415cd683c0

Subscribe to this mod's changes

developer is a skill published in the GitHub repository P47Phoenix/Claude-Plugins (2 stars, last pushed 3mo ago), licensed MIT. It adds 160 tokens to every session and 3,639 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Code reviewDebuggingTesting
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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…

openai/codex · 114 tokens

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…

openai/codex · 113 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 170 tokens