A general guide for software development work, including writing, changing, reviewing, testing, and debugging code.

It covers implementation, refactoring, code review, debugging, tests, CI, build files, scripts, migrations, infrastructure code, and software design.

It helps an agent choose the relevant guidance for the kind of programming task it is handling.

coding — Skill by AnthonyPoschen

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/anthonyposchen/agent-skills/coding

Any agent

npx skills add AnthonyPoschen/agent-skills --skill coding

Clone the repo

git clone --depth 1 https://github.com/AnthonyPoschen/agent-skills

Made for: Claude Code, Codex.

Per session 84 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 819 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. 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.

Model	Per session	Once invoked
Fable 5	$0.00084	$0.00819
Opus 5	$0.00042	$0.00409
Sonnet 5	$0.00017	$0.00164
Haiku 4.5	$0.00008	$0.00082

Measured 2d ago against content hash bc4c042403a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

coding 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.

skills/coding/SKILL.md · 76 lines

How it starts

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

Coding

Use this skill as the entrypoint for software work. Keep this file in context, then load the smallest relevant reference set for the task.

Routing

For writing new code or extending behavior, read ./references/implementation.md.
For refactoring, cleanup, simplification, extraction, restructuring, or rewrite work, read ./references/refactoring.md.
For code review, PR review, diff critique, or risk assessment, read ./references/review.md.
For debugging, failing tests, regressions, runtime errors, CI failures, or bug fixes, read ./references/debugging.md.
For architecture, API design, module boundaries, dependency direction, or design-only discussion, read ./references/design.md.
For a consequential new data model, shared scaffold, or concurrent state, also read ./references/foundations.md.
For a new application or subsystem, source file placement, package or module placement, file moves, file splits, or layout discussion, read ./references/file-organization.md.
For Go application layout, package placement, or Go file organization, also read ./references/go.md.
For choosing tests or verification, especially for persistence, framework, service, CLI, or UI behavior, read ./references/verification.md.
For shared code-quality rules, read ./references/standards.md whenever writing or changing code, and as needed during review/design.
For assertion strategy (invariant checks, debug-vs-production assert decisions, and fail-fast contracts), read ./references/assertions.md when writing or reviewing code that validates internal assumptions.

Load only the references needed for the user's current request. If a loaded reference describes ordered phases, run every remaining phase until its completion check. Load the next reference when that phase starts. Do not stop after the first phase, including subtraction. After a phase that changes the tree, commit it with git-commit-workflow, then continue the next phase.

Read the full file on GitHub · 76 lines

Files

What ships with it

18 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.

2d ago First seen · 76 lines · 84 tokens per session scan A bc4c042403a8

Subscribe to this mod's changes

coding is a skill published in the GitHub repository AnthonyPoschen/agent-skills (2 stars, last pushed 3d ago), licensed MIT. It adds 84 tokens to every session and 819 once invoked, about $0.0004 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-31.

systematic-debugging

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

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 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