workspace-improver

workspace-improver is a skill for Claude Code, Codex from regen-coordination/org-os-template. It costs 19 tokens per session (1,721 once invoked), scanned A, original, MIT.

An iterative workflow for improving an organisation's workspace through small, measured experiments. It uses project directions, task priorities, evaluation metrics, and experiment logs to guide each improvement cycle.

In plain words
What is it for?
It helps inspect workspace instructions and recent activity, select improvement opportunities, run scoped experiments, and record their results.
Why use it?
Workspace changes can become repetitive or unfocused without a record of goals and results. This workflow helps agents choose improvements and avoid repeating unsuccessful work.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps inspect workspace instructions and recent activity, select improvement opportunities, run scoped experiments, and record their results.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/regen-coordination/org-os-template/workspace-improver
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 regen-coordination/org-os-template --skill workspace-improver
Clone the repo
git clone --depth 1 https://github.com/regen-coordination/org-os-template

Made for: Claude Code, Codex.

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 workspace-improver

README.md
[![agentmods](https://agentmods.dev/badge/skills/regen-coordination/org-os-template/workspace-improver/github.svg)](https://agentmods.dev/skills/regen-coordination/org-os-template/workspace-improver)
Your own site
<a href="https://agentmods.dev/skills/regen-coordination/org-os-template/workspace-improver"><img src="https://agentmods.dev/badge/skills/regen-coordination/org-os-template/workspace-improver/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 workspace-improver

Your own site · 80×15
<a href="https://agentmods.dev/skills/regen-coordination/org-os-template/workspace-improver"><img src="https://agentmods.dev/badge/skills/regen-coordination/org-os-template/workspace-improver.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,721 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.00019 $0.01721
Opus 5 $0.00010 $0.00860
Sonnet 5 $0.00004 $0.00344
Haiku 4.5 $0.00002 $0.00172

Measured 8d ago against content hash 32462e420b70, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

workspace-improver 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 8d 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/workspace-improver/SKILL.md · 223 lines

How it starts

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

Workspace Improver

When to Use

Activate for autonomous workspace improvement sessions. This skill implements the autoresearch pattern — agents iteratively improve the workspace through scoped experiments with clear metrics.

Activate when:

  • Operator says "improve the workspace" or "run autoresearch"
  • During scheduled autonomous sessions
  • When MASTERPLAN.md activations list improvement areas
  • As part of the ongoing learning phase (Phase 3 of bootstrapping)

The Autoresearch Loop

Inspired by karpathy/autoresearch:

MASTERPLAN.md          = program.md     (human directions)
data/*.yaml + skills/  = train.py       (editable surface)
HEARTBEAT.md metrics   = val_bpb        (evaluation criteria)
memory/YYYY-MM-DD.md   = experiment log (results)

Procedure

Step 1: Read Directions

  1. Read MASTERPLAN.md — understand current activations and research directions
  2. Read HEARTBEAT.md — understand active tasks and priorities
  3. Read memory/ (last 3 days) — understand recent work and avoid repetition

Step 2: Identify Improvement

Scan for improvement opportunities in priority order:

Priority 1: MASTERPLAN Activations

  • Are there unchecked activations in MASTERPLAN.md?
  • Pick the highest-priority one that can be scoped to a single session

Priority 2: Data Gaps

  • Are there TBD, null, or placeholder values in data/*.yaml?
  • Are any registries significantly incomplete?
  • Are dates stale (last_updated > 7 days ago)?

Priority 3: Knowledge Gaps

  • Run npm run compile:knowledge to refresh the knowledge extract and compiled pages
  • Run npm run lint:knowledge — address any hard failures
  • Check for domains with coverage: "none" or "partial" in data/knowledge-manifest.yaml
  • Check for <!-- LLM-SYNTHESIZE --> markers — invoke knowledge-curator in Compilation Mode to synthesize
  • Are there sources in data/sources.yaml that haven't been processed?
  • After changes, run npm run knowledge to validate the full pipeline

Read the full file on GitHub · 223 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. 8d ago First seen · 223 lines · 19 tokens per session scan A 32462e420b70

Subscribe to this mod's changes

workspace-improver is a skill published in the GitHub repository regen-coordination/org-os-template (5 stars, last pushed 6d ago), licensed MIT. It adds 19 tokens to every session and 1,721 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-09-03.

Related

Other skills, from other repositories