write-maintainable-code

write-maintainable-code is a skill for Claude Code from Ezra144israel/governed-agent-skills. It costs 67 tokens per session (981 once invoked), scanned A, original, MIT.

A coding guide for choosing the smallest maintainable implementation that meets an already approved result. It compares possible approaches and checks that the chosen code remains understandable and within its assigned responsibility.

In plain words
What is it for?
Use it after the goal and acceptance checks are fixed to compare implementation routes, choose the right ownership boundary, and verify the resulting code.
Why use it?
It helps avoid unnecessary abstractions and keeps code easier to read and maintain over time.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the governed plugin — 6 skills shipped together

Good fit Use it after the goal and acceptance checks are fixed to compare implementation routes, choose the right ownership boundary, and verify the resulting code.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ezra144israel/governed-agent-skills/write-maintainable-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 Ezra144israel/governed-agent-skills --skill write-maintainable-code
Clone the repo
git clone --depth 1 https://github.com/Ezra144israel/governed-agent-skills

Made for: Claude Code.

Or install governed, the plugin that ships this one along with the rest of its 6 skills.

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-maintainable-code

README.md
[![agentmods](https://agentmods.dev/badge/skills/ezra144israel/governed-agent-skills/write-maintainable-code/github.svg)](https://agentmods.dev/skills/ezra144israel/governed-agent-skills/write-maintainable-code)
Your own site
<a href="https://agentmods.dev/skills/ezra144israel/governed-agent-skills/write-maintainable-code"><img src="https://agentmods.dev/badge/skills/ezra144israel/governed-agent-skills/write-maintainable-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-maintainable-code

Your own site · 80×15
<a href="https://agentmods.dev/skills/ezra144israel/governed-agent-skills/write-maintainable-code"><img src="https://agentmods.dev/badge/skills/ezra144israel/governed-agent-skills/write-maintainable-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 981 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00067 $0.00981
Opus 5.5 $0.00027 $0.00392
Sonnet 5.5 $0.00013 $0.00196
Haiku 4.5 $0.00007 $0.00098

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

Security

Grade A, and why

write-maintainable-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 1mo 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/write-maintainable-code/SKILL.md · 99 lines

How it starts

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

Write maintainable code

Use the fewest concepts that satisfy the approved result and its acceptance evidence. Minimize maintenance burden, not raw line count.

Keep the ownership boundary

  • reasoning-doctrine owns the stage, outcome, scope, evidence, route recommendation, hard stops, and the transition to execution.
  • governed-operator owns authority, seats, formal contracts, verdicts, publication, and Done.
  • This skill owns route comparison, ownership seams, concept control, readability, and implementation verification.

If outcome, acceptance evidence, or authority is unresolved, return to its owner. Apply this lens only to the selected route and safe slice. A finished change needs independent review.

Compare routes before adding code

  1. Restate the fixed result and acceptance evidence without reopening them.
  2. Inspect current code and reuse candidates. Compare current behavior, configuration, reuse, adaptation, replacement, new code, deletion, documentation, and no-code routes. If the current evidence already passes, make no change.
  3. Compare the strongest simpler alternative. Choose a route only when the fixed acceptance evidence can prove it.
  4. Name the smallest ownership seam and the concepts the selected route needs. Give each new responsibility a concrete reason tied to the accepted outcome. Name tempting concepts the result does not need.

Choose reuse when it is the better total solution. Existing code alone is no reason to require reuse or reject new code. Compare simplicity, safety, clarity, coupling, and maintenance cost. Existing tools, frameworks, vendor implementations, standards, protocols, and delivery systems are options. Building a capability, connection, protocol, or delivery mechanism remains valid when it is the better lawful solution. Neither reuse nor custom work wins without evidence.

For an implementation return or an engineering proposal required by governed-operator, name the inspected source and reuse candidates, what to reuse, adapt, replace, or build and why, the strongest simpler alternative, necessary new responsibilities, material placement and dependency choices, verification and meaningful negative cases, and unresolved prerequisites or decisions that could change implementation. Keep this evidence short. That owner decides when a proposal is required and how it returns. This skill creates no proposal or approval gate.

Read the full file on GitHub · 99 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. 1mo ago Changed · +21 lines e01e1199a360
  2. 1mo ago Changed · +6 lines 982b078511ae
  3. 1mo ago First seen · 72 lines · 67 tokens per session scan A e179eb30806b

Subscribe to this mod's changes

write-maintainable-code is a skill published in the GitHub repository Ezra144israel/governed-agent-skills (22 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 981 once invoked, about $0.0003 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-08-30.

Related

Other skills, from other repositories

hinge-profile-optimizer

Improve a Hinge dating profile through research-backed screenshot audits, photo selection and ordering, conversational discovery, prompt and caption writing, settings review, or post-launch troubleshooting. Use for a full profile rebuild or a focused request about photos, copy, positioning, match quality, or profile…

b1rdmania/hinge-profile-optimizer · 63 tokens

source

Ask registered marketplace workers (verify, escalate, consult, simulate) via MCP/REST and get structured answers back. Canonical live skill: https://app.sanctifai.com/agents/source/skill.md.

sanctifai/skills · 0 tokens

proof-of-human

Seal that a WebAuthn-authed human participated and attested an exact payload. Outsiders can verify the receipt without trusting your DB. When WebAuthn cannot run in-card, mint via this Chat bridge (POST attestation → Chrome approveurl → poll certificateurl).

sanctifai/skills · 59 tokens

update-llms

Updates the llms.txt file to reflect changes in documentation. Use when editing repository details or specifications. For creating from scratch, see create-llms.

tuliosousapro/SaaS-blueprint · 36 tokens

competitor-analysis

Structured competitor teardown skill. Use when scraping competitor sites, extracting pricing/features/positioning, or analyzing strategic gaps. For general research, see market-research.

tuliosousapro/SaaS-blueprint · 36 tokens

idea-validator

Structured validation framework that scores product ideas. Use when evaluating problem severity, willingness-to-pay, or founder-market fit. For market intelligence, see market-research.

tuliosousapro/SaaS-blueprint · 35 tokens