coder

A framework for helping an organization adopt AI, covering constraints, ownership, directives, expectations, and rewards.

In plain words
What is it for?
Use it to plan AI adoption, clarify who owns the work, set directions and expectations, and define related rewards.
Why use it?
It helps make AI adoption an organizational process with clear responsibilities and expectations, rather than leaving each person to work it out alone.

Skill for Claude CodeCodex

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/breethomas/bette-think/coder
Any agent
npx skills add breethomas/bette-think --skill coder
Clone the repo
git clone --depth 1 https://github.com/breethomas/bette-think

Made for: Claude Code, Codex.

Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 933 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00028 $0.00933
Opus 5 $0.00014 $0.00466
Sonnet 5 $0.00006 $0.00187
Haiku 4.5 $0.00003 $0.00093

Measured 2d ago against content hash ddddedd8479e, 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 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.

plugins/bette-think/skills/coder/SKILL.md · 129 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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 · 129 lines · 28 tokens per session scan A ddddedd8479e

Subscribe to this mod's changes

coder is a skill published in the GitHub repository breethomas/bette-think (16 stars, last pushed 5mo ago), with no licence file. It adds 28 tokens to every session and 933 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-30.

Related

Other skills, from other repositories

product-designer

Use when the user asks to review a design, critique a UI or mockup, give design feedback, or check a screen for usability and accessibility issues. Do NOT use for visual brand or aesthetic preference debates, or for reviewing copy before layout is settled.

aakashg/pm-claude-skills · 55 tokens

status-update-writer

Use when the user asks to write a status update, weekly or monthly update, stakeholder update, project update, standup, status report, or QBR. Do NOT use for writing a PRD or a retro doc — those need different structures.

aakashg/pm-claude-skills · 55 tokens

idea-validator

Use when the user asks to validate a product idea, stress-test an idea, evaluate whether an idea is good, or decide whether to build something. Do NOT use for prioritizing an existing backlog or reviewing a shipped feature — those need RICE scoring or a design review instead.

aakashg/pm-claude-skills · 59 tokens

linkedin-post-writer

Use when the user asks to write, draft, or rewrite a LinkedIn post, turn notes or an article into a LinkedIn post, or fix a hook that is not landing. Do NOT use for X/Twitter threads, newsletters, or blog posts — those need different length and hook rules.

aakashg/pm-claude-skills · 65 tokens

prompt-engineer

Use when the user asks to improve, optimize, rewrite, debug, or shorten a prompt, or asks why a prompt is producing bad output. Do NOT use for writing a Claude Code SKILL.md — that needs skill structure rules, not prompt techniques.

aakashg/pm-claude-skills · 55 tokens

ai-shaped-readiness-advisor

Assess whether your product work is AI-first or AI-shaped. Use when evaluating AI maturity and choosing the next team capability to build.

deanpeters/Product-Manager-Skills · 33 tokens