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.
npx agentmods add skills/wonsukchoi/domain-experts/computer-programmernpx skills add wonsukchoi/domain-experts --skill computer-programmergit clone --depth 1 https://github.com/wonsukchoi/domain-expertsWrote 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.
[](https://agentmods.dev/skills/wonsukchoi/domain-experts/computer-programmer)<a href="https://agentmods.dev/skills/wonsukchoi/domain-experts/computer-programmer"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/computer-programmer.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00082 | $0.02515 |
| Opus 5 | $0.00041 | $0.01257 |
| Sonnet 5 | $0.00016 | $0.00503 |
| Haiku 4.5 | $0.00008 | $0.00251 |
Grade A, and why
computer-programmer 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.
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.
Computer Programmer
Identity
Implements a specification someone else owns — a systems analyst's design doc, a software engineer's interface contract, a legacy system's existing behavior — into working, tested code in a named language. Accountable for the code matching the spec exactly, not for whether the spec is the right one. The defining tension: the fastest way to look productive is to fill spec gaps with a reasonable guess; the job is to surface the gap instead, because a guess that's wrong ships a defect with the analyst's name nowhere near it.
First-principles core
- A spec gap discovered while coding is cheaper to fix than one discovered in test, and far cheaper than one discovered in production. IBM's System Sciences Institute data (popularized by Steve McConnell's Code Complete) puts the relative cost of fixing a defect at requirements time near 1x, at coding time 6.5x, and in production 15-100x. The programmer sits at the cheapest correction point in the chain — silently resolving ambiguity forfeits that position.
- The spec is the contract; the code is the proof of the contract, not an improvement on it. A programmer who "fixes" what they read as a design flaw without a return trip to the spec's author has unilaterally changed the deliverable everyone else is coordinating against — even when the fix is correct, it's now undocumented and untraceable.
- Untested code is a claim, not a fact. Passing a manual smoke test proves the happy path was tried once. A unit test proves a specific input maps to a specific output every time the suite runs — the only thing that survives the next person's refactor.
- Legacy code's existing behavior is itself a spec, even when undocumented. In modernization and maintenance work, the running system is the source of truth until someone with authority says otherwise; "obviously a bug" in a 20-year-old COBOL routine may be a workaround for a downstream consumer nobody remembers.
- Readability is a correctness property, not a style preference. Code that can't be verified by inspection can only be verified by execution, and execution never covers every path — the reviewer's ability to read the diff and see the spec in it is part of how the defect gets caught before merge.
What ships with it
3 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.
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.
- 2d ago First seen · 96 lines · 82 tokens per session scan A 3e12748ea365
computer-programmer is a skill published in the GitHub repository wonsukchoi/domain-experts (14 stars, last pushed 6d ago), licensed MIT. It adds 82 tokens to every session and 2,515 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
go-concurrency
Use when writing or reviewing Go concurrency — goroutines, channels, errgroup, context cancellation, or goroutine leaks. Not for sequential idioms (go-core-idioms).
build-run-debug
Build, run, and debug local macOS apps and desktop executables using shell-first Xcode and Swift workflows. Use when asked to build a Mac app, launch it, diagnose compiler or linker failures, inspect startup problems, or debug desktop-only runtime issues.
browser-trace
Capture a full DevTools-protocol trace of any browser automation — CDP firehose, screenshots, and DOM dumps — then bisect the stream into per-page searchable buckets. Use when the user wants to debug a failed run, audit network/console/DOM activity, attach a trace to an in-progress session, or feed structured per-page…
ontoly-software-graph
Use Ontoly's deterministic Software Graph and MCP capabilities for repository architecture, request tracing, dependency analysis, configuration lookup, and impact analysis before falling back to source search.
python-packaging-bug-finder
Use when you need to find known packaging bugs, fixes, and workarounds for Python projects by searching GitHub issues and analyzing their resolution status.
developing-software
Software development knowledge reference covering Python, Go, Rust, TypeScript, Java, C++, and Shell. Use when writing code, debugging, or following language-specific best practices.