macollins27

Owner Rep — Development skill for Claude Code

Development community

A Claude Code mod that watches the coding agent for the person who owns the work: one row above the prompt, a plain-words briefing on a press, and a read-only check of the agent's claims against the r.

How to install Owner Rep

This entry records only its repository, not the path inside it, so there is no exact command to give. Open macollins27/owner-rep and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Owner Rep does

A Claude Code mod that watches the coding agent for the person who owns the work: one row above the prompt, a plain-words briefing on a press, and a read-only check of the agent's claims against the real files.

Alternatives in Development

  • Homunculus — A Claude Code plugin that watches how you work, learns your patterns, and evolves itself to help you better 315 ★
  • LiveBrowser — Browser tools (browser_navigate, browser_get_state, browser_snapshot, browser_get_text, browser_click, browser 250 ★
  • Eli5 — Say the last answer again in plain words — same facts, in the order the operator needs them 49 ★

README

Owner rep

A Claude Code mod that watches a coding agent on behalf of the person who owns the work, and reports back in plain words: what the agent has really done, what it has left out, and what to tell it next.

It is built for the owner who directs agents but does not read code. The agent's own report is the only account they get, and it is the one account that cannot be taken on trust. The rep reads the same conversation, takes nothing on the agent's word, and says so briefly.

![The briefing card, on a real session](docs/briefing.png)

What it does

The rep draws one row above the prompt, in the same shape as Claude Code's built-in "You should know" note: the result the owner wants, worked out from the owner's own messages, and what the agent is doing right now, with a mark when the session needs a look (the agent has stopped, is asking a question, or a plan is waiting for a yes). That status is plain words built from the tool's name: a file's name for a read or an edit, the program's name for a shell command, and never any text of the command itself.

Behind that row are three reads of increasing cost.

Read When How Cost
Watch Every eighth model request of a turn, and at every stop A fresh model instance over the agent's cached conversation, no tools Mostly cache reads; never blocks the agent
Briefing On a press (1 or click) Same mechanism, longer brief One model call
Check On a second press, only when chosen A separate headless claude -p run with read-only tools, over the session record and the real files Measured at about 210k fresh tokens plus 2.2M cache reads, about two minutes

The **watch** stays silent unless it finds something with a cost to the owner: work dropped or shrunk, a claim not shown, a test never run, the easy option taken in place of the right one. Then one "Heads up" line appears, with the reason beneath it.

The **briefing** is a card: where the work really st