write-code

write-code is a skill for Claude Code from nirecom/agents. It costs 26 tokens per session (2,190 once invoked), scanned A, original, MIT.

A coding workflow for editing source files for the current task. It also covers code checks and delegated repair work.

In plain words
What is it for?
Changing source code, running checks, and repairing problems found during those checks.
Why use it?
It organizes the editing process and catches issues such as lint or type-check failures.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: model in frontmatter; mentions subagents; names the AskUserQuestion tool.

Good fit Changing source code, running checks, and repairing problems found during those checks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nirecom/agents/write-code
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.

Any agent
npx skills add nirecom/agents --skill write-code
Clone the repo
git clone --depth 1 https://github.com/nirecom/agents

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for write-code

README.md
[![agentmods](https://agentmods.dev/badge/skills/nirecom/agents/write-code/github.svg)](https://agentmods.dev/skills/nirecom/agents/write-code)
Your own site
<a href="https://agentmods.dev/skills/nirecom/agents/write-code"><img src="https://agentmods.dev/badge/skills/nirecom/agents/write-code/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for write-code

Your own site · 80×15
<a href="https://agentmods.dev/skills/nirecom/agents/write-code"><img src="https://agentmods.dev/badge/skills/nirecom/agents/write-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,190 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00026 $0.02190
Opus 5.5 $0.00010 $0.00876
Sonnet 5.5 $0.00005 $0.00438
Haiku 4.5 $0.00003 $0.00219

Measured 4d ago against content hash fcd8acf4720d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

write-code 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 4d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/detect-contract-pins.sh, scripts/self-check-siblings.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/write-code/SKILL.md · 96 lines

How it starts

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

Edit source code for the current task.

Procedure

WCD-0. Read the session facts once, before the pre-launch steps that consume them: node "$AGENTS_MAIN_ROOT/bin/workflow/read-session-facts" --session "$SESSION_ID"

  • PLANS_DIR= (substitute for every <PLANS_DIR> below) and GATE_CONFIRM_CODE= (the WCD-2 gate: ON/OFF/ERROR).
  • If the command exits non-zero, or PLANS_DIR=NONE, stop — do not proceed with any step that uses <PLANS_DIR>; report via /supervisor-report; never construct a path like NONE/<session-id>-.... When a hook blocks a sanctioned command, a fallback path is taken, or any unexpected outcome occurs, report via /supervisor-report (trigger conditions: rules/supervisor-reporting.md). Read rules/ops.md before any destructive or system-state-changing command (including inside WCD-4 self-repair) — on-demand-only, never auto-injected; it owns the recovery-options-first decision path.

WCD-1. Read rules/core-principles.md, rules/coding.md (on-demand-only: not auto-injected, so this Read is the only way it arrives), and the target files identified from the plan.

WCD-2. CONFIRM_CODE gate — enumerate planned edits (one line per file: path + change intent).

  • Write every file you plan to edit, one path per line (repo-relative, nothing else on the line), to <PLANS_DIR>/<session-id>-write-code-files.txt with the Write tool.
  • Keep that list complete: it is the sole input of the S1b and S4 signals judged in WCD-3.
  • Then branch on GATE_CONFIRM_CODE from WCD-0 — OFF: proceed to WCD-3; ON or ERROR: present the planned edits via AskUserQuestion and wait for approval before continuing.

WCD-3. Always follow skills/_shared/jev-two-stage-judge.md with point=complexity-judge stage=write-code (S1b and S4 come only from the WCD-2 list, so no stored evaluation is reused); use its model= and SIGNALS_CSV — never judge the level inline. Emit in Claude text output (NOT Bash echo): > Model selected: **<model alias>** (signals: [comma-separated triggered signal IDs, or "none"]) WCD-3a. Emit echo "<<WORKFLOW_MARK_STEP_write_code_in_progress>>" via Bash immediately before the WCD-4 subagent launch.

WCD-4. Launch subagent (Agent tool, mode: "default", model: <model alias from WCD-3> — the model alias, never the level high / low) with a prompt containing:

  • Target files and planned edit summary from WCD-2.
  • A-layer language essence block (see below).
  • Directive: "Read rules/coding.md (the hub — on-demand-only, so it does not reach you otherwise) and rules/coding/<lang>.md for each language present, before the first Edit."
  • Directive: "Read rules/shell-commands.md before the first Bash command, or before writing a file — general-purpose dispatch does not inherit auto-injected rules."
  • The canonical line of the rules/shell-commands.md Subagent Dispatch Prompts section, verbatim as a standalone line, with <AGENTS_MAIN_ROOT> replaced by the literal absolute path.
  • Directive: "Read rules/user-escalation.md before any system-state-changing command — general-purpose dispatch does not inherit auto-injected rules."
  • Directive: "Read rules/ops.md before any destructive or system-state-changing command inside self-repair — general-purpose dispatch does not inherit auto-injected rules; on-demand-only, so it does not reach you otherwise."
  • (Optional) Follow agents/lib/nfr-severity-calibration.md to obtain the PROJECT NFR block and use it as an implementation constraint when relevant.
  • Lint/typecheck recipe table (see below).
  • Self-repair cap: 3 iterations; if still failing after 3, surface tool output verbatim.
  • Lint-tool absence policy: when a tool is unavailable, skip that check AND emit <tool> not found — check skipped in the final summary. Never omit this notice.
  • Scope-expansion policy: if editing reveals additional files not in the original list need changes, include them in the final summary with a reason. Do NOT prompt mid-edit; do NOT silently expand scope.
  • Prohibitions: no diffs shown in the conversation; no mid-edit confirmation prompts. WCD-5. Parse the subagent summary. Surface tool output on failure. Collect all check skipped notes and scope-expansion notes.

Read the full file on GitHub · 96 lines

Files

What ships with it

2 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. 4d ago Changed · +1 lines fcd8acf4720d
  2. 7d ago Changed · -3 lines 58dc13b85c9c
  3. 9d ago Changed · +1 lines 3f40a1793f6a
  4. 11d ago Changed 083f248d63fe
  5. 17d ago Changed 8f37d57418aa
  6. 20d ago Changed · +2 lines bebbb408e86d
  7. 21d ago Changed · +4 lines 7fc52eef96d3
  8. 25d ago Changed d0ca5bfad773
  9. 1mo ago Changed 9304e5a93264
  10. 1mo ago First seen · 91 lines · 26 tokens per session scan A b8d06618870a

Subscribe to this mod's changes

write-code is a skill published in the GitHub repository nirecom/agents (3 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 2,190 once invoked, about $0.0001 per session on Opus 5.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-09-03.

Related

Other skills, from other repositories

orbit-notion

Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…

nexu-io/open-design · 117 tokens

agentmail

Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.

paperclipai/paperclip · 30 tokens

rowboat-spaces

How to work as a member of Rowboat Spaces, the team chat where people and agents work together. Load it once per session, before acting on any request that reaches you from Rowboat; it covers your setup, mentions and hand-offs, the tools, and files.

rowboatlabs/rowboat · 60 tokens

feishu

Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.

Hmbown/CodeWhale · 33 tokens

pinchtab-mcp

Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.

pinchtab/pinchtab · 52 tokens

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens