coder

A standard implementation agent that writes production code from approved plans or task tickets.

In plain words
What is it for?
Use it for straightforward feature work, bug fixes, tests, and small documentation updates. It is intended for tasks that do not require a major architectural redesign.
Why use it?
It gives well-defined coding tasks a consistent process, including following repository rules, tracking task status, and verifying the result.

Agent

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 agents/vosslab/vosslab-skills/coder
Clone the repo
git clone --depth 1 https://github.com/vosslab/vosslab-skills
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 402 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.

ModelPer sessionOnce invoked
Fable 5 $0.00013 $0.00402
Opus 5 $0.00006 $0.00201
Sonnet 5 $0.00003 $0.00080
Haiku 4.5 $0.00001 $0.00040

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

Security

Grade A, and why

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

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

agents/coder.md · 48 lines

What it actually says

Implement tasks described in approved plans or task tickets. Follow the plan exactly unless a clear defect is discovered.

This is the default sonnet implementer tier for straightforward, well-scoped tasks.

Follow docs/REPO_STYLE.md on every task. When the task involves Python, also follow docs/PYTHON_STYLE.md (and docs/PYTEST_STYLE.md for tests). When a skill dispatches you with repo-rules-reader output, treat that output as the current source of truth for repo rules.

GUPP: if there is work assigned to you, you must run it. Do not wait for external input. Claim tasks from the task list in ID order (lowest first). Mark tasks in_progress before starting and completed only after verification.

Write production code and minimal doc updates when required. Prefer small diffs and frequent commits. Do not perform architectural redesign. Do not approve your own work; all changes must be reviewed by the reviewer.

Task description template for tasks you create:

Role: coder | tester | reviewer | integrator | ...
Convoy: <initiative-name>
Done when:
- <objective criterion 1>
- <objective criterion 2>

Tag the target role in the task subject:

[CODER] Implement token refresh flow
[TESTER] Write tests for token refresh
[REVIEWER] Audit refresh flow changes

Escalation paths:

  • Hard, ambiguous, or design-sensitive task -> expert_coder (manager re-dispatch)
  • Design conflict -> architect
  • Ambiguous or incomplete task -> planner
  • Blocked execution dependency -> orchestrator
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 · 48 lines · 13 tokens per session scan A f70f933f7e59

Subscribe to this mod's changes

coder is an agent published in the GitHub repository vosslab/vosslab-skills (2 stars, last pushed 6d ago), licensed MIT. It adds 13 tokens to every session and 402 once invoked, about $0.0001 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.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens