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 skills add kouroshez/coding-os --skill thinking_osgit clone --depth 1 https://github.com/kouroshez/coding-osWrote 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/kouroshez/coding-os/thinking_os)<a href="https://agentmods.dev/skills/kouroshez/coding-os/thinking_os"><img src="https://agentmods.dev/badge/skills/kouroshez/coding-os/thinking_os.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.00061 | $0.03580 |
| Opus 5 | $0.00030 | $0.01790 |
| Sonnet 5 | $0.00012 | $0.00716 |
| Haiku 4.5 | $0.00006 | $0.00358 |
Grade A, and why
thinking_os 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 4d 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 — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Thinking OS — Full Methodology
Purpose
Complement the always-active Kernel rule (thinking_os.md, in your adapter's rules dir) with the complete Zoom cycle, Process Manager, and 10 Thinking Tools. Load this skill when the Complexity Gate returns COMPLICATED or COMPLEX. Source of truth: consumer projects read docs/workflow/thinking_os-final-edition.md (copied by cos init); the meta-repo canonical lives at src/core/docs/thinking_os-final-edition.md.
Naming note: the skill slug
thinking_osintentionally keeps the underscore to mirror thethinking_osPython subsystem it fronts (other skills use kebab-case). A deliberate, documented exception to the kebab-case convention — not an oversight.
Kernel Decisions (Detailed)
Complexity Gate (Depth Routing)
Gate classification (Q1 + Q2) is handled by the always-active rule. Use this matrix to determine depth of analysis:
│ 1 dim │ 2-4 dim │ 5+ dim
────────────────┼───────────────┼─────────────────┼─────────────────
CLEAR │ Just do it │ Quick checklist │ Rare — batch it
COMPLICATED │ Single Zoom In│ Light Zoom cycle │ Full Zoom cycle
COMPLEX │ Probe + test │ Zoom + test/dim │ Full Zoom + prototype
CHAOTIC │ Act now │ Act now, Zoom │ Act now, Zoom later
CONFUSION │ Break it down │ Break it down │ Separate problems
For COMPLEX problems, activate Experiment Protocol before full Zoom In:
- HYPOTHESIS: "I believe [X] will work because [Y]."
- SMALLEST TEST: cheapest/fastest way to validate
- SUCCESS/FAILURE SIGNALS: measurable metrics
- TIMEBOX: max time before deciding
- LEARN: update Orient and continue
Zoom Out
First Zoom Out (before any work):
- IDENTIFY DIMENSIONS — independent aspects of the problem
- PRIORITY HEURISTIC — which dimension first?
- (a) DEPENDENCY: most dependencies → build first
- (b) UNCERTAINTY: most unknowns → validate early
- (c) BOTTLENECK: blocks others → unblock it
- (d) EVOLUTION (Wardley): novel → deep analysis, commodity → best practice
- Priority: (c) > (a) > (b) > (d)
- ASSIGN DEPTH per dimension: Deep / Medium / Light
- ASSIGN PHASE per dimension: MVP / v1 / v2
- FLAG UNKNOWNS — state assumptions explicitly
What ships with it
1 file 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.
- 4d ago First seen · 289 lines · 61 tokens per session scan A c8ca8091265e
thinking_os is a skill published in the GitHub repository kouroshez/coding-os (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 61 tokens to every session and 3,580 once invoked, about $0.0003 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
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…
backfill-enumerate-drain
How to backfill a newly-added repo or team — the enumerate-then-drain loop, the single-event contract, and resume-safe todo discipline. Load this when handling a .added seed event with the planner on.
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-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-infra-architecture
Use for project infra and architecture context: environments, adapters, runtime configuration, deployments, service dependencies, datastores, API contracts, ownership, incidents, and dependency blast radius.
slides
A slide generator that creates PNG images for presentation decks, including simple backgrounds for spoken-video scripts and fuller layouts for standalone presentations.