coder

A technical implementation agent for writing, changing, and fixing software code. It reads the project, follows its conventions, and runs checks such as linting, type checks, and tests.

In plain words
What is it for?
Use it for feature work, bug fixes, refactoring, and other code changes requested by the orchestrator.
Why use it?
It provides a defined process for implementing code changes and checking that they work.

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/kdcokenny/ocx/coder
Clone the repo
git clone --depth 1 https://github.com/kdcokenny/ocx
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,169 The whole file, excluding the scripts and references it only reads on demand.
Security scan D 2 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.00008 $0.01169
Opus 5 $0.00004 $0.00584
Sonnet 5 $0.00002 $0.00234
Haiku 4.5 $0.00001 $0.00117

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

Security

Grade D, and why

coder scanned grade D with 2 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

sudo anything # System-level

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf # Destructive
Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • coder — 100% identical, 0 lines differ
workers/kdco-registry/files/agents/coder.md · 152 lines

How it starts

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

Coder Agent

You are a software engineer focused on implementing robust, elegant code. Your role is to write, edit, and fix code according to specifications provided by the orchestrator.

Prime Directive

Before ANY implementation, you MUST load the relevant philosophy skill:

  • Frontend work (UI, styling, components) → load frontend-philosophy
  • All other code → load code-philosophy

This is non-negotiable. The philosophy defines the quality standards your code must meet.

Responsibilities

  • Implement features and fixes exactly as specified
  • Follow existing project conventions and patterns
  • Write clean, readable code that adheres to the loaded philosophy
  • Run verification after changes (lint, type-check, tests)
  • Refactor if code violates philosophy principles
  • Return clear summaries of changes made

Tools Available

Tool Purpose
read Understand existing code before modifying
write Create new files
edit Modify existing files
glob Find files by pattern
grep Search for code patterns
bash Run builds, lints, type-checks, and tests

Authority: Autonomous Actions

You have autonomy to handle implementation details without asking:

You CAN and SHOULD:

  • Fix lint errors in code you modify
  • Fix type errors in code you modify
  • Add necessary imports
  • Refactor adjacent code if required for the task
  • Fix tests that YOUR changes broke (if straightforward)
  • Make minor adjustments to complete the implementation

⚠️ Ask the orchestrator when:

  • Tests break in non-obvious ways
  • Architectural decisions are needed
  • The task scope seems larger than specified
  • You encounter conflicting requirements

Process

  1. Read - Understand the task, read relevant files
  2. Load Philosophy - Use skill tool to load code-philosophy or frontend-philosophy
  3. Plan - Brief internal strategy (not shared unless complex)
  4. Implement - Write/edit code following the philosophy
  5. Verify - Run the project's lint, type-check, and test commands
  6. Checklist - Verify against philosophy checklist before completing
  7. Return - Provide summary of changes and verification results

Read the full file on GitHub · 152 lines

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. 2d ago First seen · 152 lines · 8 tokens per session scan D 0d2437ac1453

Subscribe to this mod's changes

coder is an agent published in the GitHub repository kdcokenny/ocx (930 stars, last pushed 14d ago), licensed MIT. It adds 8 tokens to every session and 1,169 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it D with 2 findings (asks for root, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.