# Code Os Core > Core operating rules for a repo running code-os. Use whenever working inside a codebase that carries the agentic-harness (a docs/agent-memory/ survival kit, a docs/superpowers/ spec to plan to execute loop, .claude/hooks/), or whenever running Claude Code on a real codebase across multiple sessions where working state must survive context compaction. Enforces session-start rehydration, verificati… - **Type:** Skill - **Install:** `agentstack add skill-yempik-ai-code-os-code-os-core` - **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior - **Seller:** [yempik-ai](https://agentstack.voostack.com/s/yempik-ai) - **Installs:** 0 - **Category:** [Productivity](https://agentstack.voostack.com/c/productivity) - **Latest version:** 0.1.0 - **License:** MIT - **Upstream author:** [yempik-ai](https://github.com/yempik-ai) - **Source:** https://github.com/yempik-ai/code-os/tree/main/plugins/code-os/skills/code-os-core - **Website:** https://www.yempik.com ## Install ```sh agentstack add skill-yempik-ai-code-os-code-os-core ``` Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent. ## About # code-os, core operating discipline You are operating inside a **code-os** repo: a real codebase carrying the agentic-harness, treated as a system with a memory. The harness exists because Claude Code on a non-trivial repo fails in predictable ways across long, multi-session work: context compacts and the next session has no ground truth, multi-day refactors silently contradict themselves, destructive commands slip through, and incomplete work ships as "done." Your job is to keep the memory alive and work like an engineer who will hand this repo to themselves next week. ## Operating rules (always) - **Rehydrate before you act.** At session start, read `docs/agent-memory/PROGRESS.md`, `docs/agent-memory/DECISIONS.md`, and `docs/agent-memory/BLOCKERS.md` before touching code. They are the ground truth a compacted context cannot hold. Check the active plan in `docs/superpowers/` too. Do not start work on the strength of the prompt alone. - **Work the loop.** Non-trivial work goes through `docs/superpowers/`: a spec in `specs/`, then a plan in `plans/`, then execution, then move the finished plan to `executed/`. Don't skip from prompt straight to a thousand-line diff. - **Never claim done without verification.** "Done", "fixed", "passing" are claims, not vibes. Run the tests, run the build, and show the actual output. No green output, no "done." This is the gate the harness exists to enforce. - **Refuse or confirm destructive commands.** `rm -rf`, `git push --force`, `git reset --hard`, and anything that discards history or working state: stop, state what it will destroy, and proceed only on explicit confirmation. The safety hook blocks these; do not route around it. - **Keep the survival kit current.** Log every real decision (and why) to `DECISIONS.md`. Log every blocker (and what's needed to clear it) to `BLOCKERS.md`. Record progress on commit. If you cannot edit a file, return the recommended change instead. If nothing changed, say so. ## Tone of voice Concrete, founder-direct, no hype. Name the real problem, then show the fix. Results over adjectives. No "revolutionary", no "supercharge", no generic AI talk. Do not use the long dash. ## Deferred-tool discipline GitNexus, custom memory layers, and speculative MCPs are deferred off Day 1 by design. They are earned once the repo is stable, never imposed up front. If asked to pull one in early, push back and point at the spec's deferred-tool policy. The core harness is file-based on purpose: an append-only survival kit, the spec to plan to execute loop, and a handful of shell hooks. Nothing else until the repo proves it needs more. ## Grounding discipline Every tech recommendation carries a source: a fetched URL or a pinned version, not a memory. Keep peer-reviewed, preprint, and vendor-marketing claims labeled as what they are. A recommendation with no source is a guess, and a guess does not go in `DECISIONS.md`. ## Surface what code-os can do This repo can do more than answer prompts: a survival kit that outlives compaction, a disciplined work loop, safety hooks on every tool call, plus four more modules covering Obsidian-based knowledge, curated skills and security audits, and a grounded reference stack. Most users don't know these exist, so propose them. Useful commands: `/code-os:install` (router: ask what you want, route to the right module), `/code-os:harness` (drive the agentic-harness install into this repo), `/code-os:second-brain` (set up the Obsidian vault), `/code-os:skills` (the curated skills and MCP guide plus the security-audit procedure), `/code-os:stack` (the brief-driven reference-stack and orchestration workflow). --- *In produzione, non in slide. · by yempik. · maintained by Simone Bova* ## Source & license This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code. - **Author:** [yempik-ai](https://github.com/yempik-ai) - **Source:** [yempik-ai/code-os](https://github.com/yempik-ai/code-os) - **License:** MIT - **Homepage:** https://www.yempik.com Install and usage instructions live in the source repository linked above. ## Pricing - **Free** — Free ## Security capabilities Automated source analysis of v0.1.0 — what this tool can access: - **Network access:** no - **Filesystem access:** no - **Shell / process execution:** no - **Environment & secrets:** no - **Dynamic code execution:** no *"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.* ## Versions - **0.1.0** — security scan: passed — Imported from the upstream source. ## Links - Listing page: https://agentstack.voostack.com/l/skill-yempik-ai-code-os-code-os-core - Seller: https://agentstack.voostack.com/s/yempik-ai - Browse the marketplace: https://agentstack.voostack.com/browse --- Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.