agentmods.dev

meta-engineering

meta-engineering is a skill for Claude Code, Codex from kouroshez/coding-os. It costs 83 tokens per session (1,968 once invoked), scanned A, original, Apache-2.0.

A set of rules for changing the coding-os project itself, including its core code, command-line tools, adapters, templates, and hooks. It explains how changes flow from shared source code into generated project-specific files.

In plain words
What is it for?
Use it when editing the meta-repository's core systems, command-line tools, adapters, templates, hooks, or regeneration workflows.
Why use it?
It helps prevent a change in the central project from breaking the many projects that consume its generated output.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions AGENTS.md; mentions Codex.

not rated 6repo yesterday A scan 83 tokens original Apache-2.0

Good fit Use it when editing the meta-repository's core systems, command-line tools, adapters, templates, hooks, or regeneration workflows.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kouroshez/coding-os/meta-engineering
View source ↗ kouroshez/coding-os coding-os.dev
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 kouroshez/coding-os --skill meta-engineering
Clone the repo
git clone --depth 1 https://github.com/kouroshez/coding-os

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 meta-engineering

README.md
[![agentmods](https://agentmods.dev/badge/skills/kouroshez/coding-os/meta-engineering/github.svg)](https://agentmods.dev/skills/kouroshez/coding-os/meta-engineering)
Your own site
<a href="https://agentmods.dev/skills/kouroshez/coding-os/meta-engineering"><img src="https://agentmods.dev/badge/skills/kouroshez/coding-os/meta-engineering/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 meta-engineering

Your own site · 80×15
<a href="https://agentmods.dev/skills/kouroshez/coding-os/meta-engineering"><img src="https://agentmods.dev/badge/skills/kouroshez/coding-os/meta-engineering.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 83 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,968 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.00083 $0.01968
Opus 5 $0.00042 $0.00984
Sonnet 5 $0.00017 $0.00394
Haiku 4.5 $0.00008 $0.00197

Measured 5d ago against content hash b0339547e016, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

meta-engineering 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 5d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/which_layer.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

src/templates/meta/skills/meta-engineering/SKILL.md · 152 lines

How it starts

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

meta-engineering

Purpose: Internalise that every line of code in this repo eventually ships to N consumer projects and act accordingly. Without this skill, agents treat meta-repo files like a normal app — they grep, they edit, they break consumers.

Read when: editing src/core/**/*.py, src/cli/**/*.py, src/adapters/**/*.py, src/core/hooks/*.sh, src/core/hooks/_helpers/*.py, src/templates/**/stack.yaml, or src/core/hooks/registry.yaml.

Skip when: editing docs/, tests/, or .coding-os/ runtime state.

The DNA → mRNA → phenotype contract

core/             ── DNA          ─ agent + stack agnostic
src/adapters/<id>/    ── mRNA         ─ per-agent translation
src/templates/<id>/   ── phenotype    ─ per-stack overlay
            ↓ cli/  (factory)
consumer project  ── organism     ─ Django+Claude, Next+Codex, …

Before any edit, ask: which layer does this belong in? Mis-layering is the most common meta-repo bug. If unsure, default to lower layer (more reuse) and split when a single agent or stack genuinely diverges.

Mandatory pre-edit moves (order matters)

  1. Graph context first — non-negotiable for src/core/**/*.py, src/cli/**/*.py, src/adapters/**/*.py:

    • cos_graph_context(file_or_uid, depth=1) — what's connected.
    • cos_graph_references(uid) — who depends on the symbol.
    • For a rename: cos_graph_rename_plan(uid, new_name) BEFORE first Edit.
    • For a refactor: cos_graph_impact(uid, depth=3). The enforce-graph-context.sh hook records the marker for you.

  2. Skill stack — load Skill graph-explorer (primary), then Skill clean-code. COMPLICATED+ adds Skill thinking_os.

  3. Doc anchor — every code edit must trace to a documented spec (PRD / playbook / engineering rule). The enforce-doc-anchor.sh hook BLOCKS edits without a .doc-anchor marker.

  4. Task marker — governance / hook-registry / rule-SSOT edits require .task-current to name a governance|docs-update|template-update task. block-protected-files.sh enforces.

Read the full file on GitHub · 152 lines

Files

What ships with it

2 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.

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. 5d ago First seen · 152 lines · 83 tokens per session scan A b0339547e016

Subscribe to this mod's changes

meta-engineering is a skill published in the GitHub repository kouroshez/coding-os (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 83 tokens to every session and 1,968 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.

Building agentsClaude Codeai-agentscodexdeveloper-toolsknowledge-graphmcp
Related

Other skills, from other repositories

potpie-graph

Use when the task can read or write the project-memory graph through the potpie CLI: discover the contract with graph catalog, read named views with graph read, resolve entity identity with graph search-entities, create validated plans with graph propose, commit plans with graph commit --verify, inspect quality with…

potpie-ai/potpie · 94 tokens

potpie-source-ingestion

Use when the user explicitly asks to ingest, refresh, or deeply understand a repository, PR, issue, ticket, runbook, incident report, document, or web link into Potpie. The harness performs todo-driven discovery, uses local/GitHub/integration tools and read-only subagents when available, builds evidence-backed…

potpie-ai/potpie · 82 tokens

potpie-repo-baseline

Use when establishing, refreshing, or deeply understanding a repository's baseline memory in Potpie: purpose, application type, features, services/modules, environments, deploy shape, dependencies, API contracts, datastores, integrations, ownership, and explicit preferences. The harness reads authored and…

potpie-ai/potpie · 75 tokens

graph-mutation-plan

Cookbook for composing an applygraphmutations plan — stable entitykey patterns, the canonical label/edge vocabulary, evidence/invalidation/confidence discipline, and a worked example. Load this when building a non-trivial mutation plan.

potpie-ai/potpie · 51 tokens

potpie-cli

Use when the task is centered on running, explaining, configuring, or troubleshooting the potpie command: doctor, login, pot management, source registration, search, graph workbench reads/writes, and pot scope behavior.

potpie-ai/potpie · 50 tokens

potpie-change-timeline

Use when an agent needs recent or historical change context: what changed recently, regressions, merged PRs, tickets, docs, incidents, deployments, releases, and source-history ingestion.

potpie-ai/potpie · 43 tokens