quickstart

quickstart is a skill for Claude Code, Codex from jacob-dietle/context-os. It costs 107 tokens per session (1,587 once invoked), scanned C, original, MIT.

A guided setup process for building a Context OS, a linked knowledge-base system that preserves information across AI sessions and helps it build on earlier work.

In plain words
What is it for?
Use it to initialize the folders, configuration, first knowledge entries, and verification steps for a new or existing collection of notes and documents.
Why use it?
It gives a new system a clear starting structure and checks whether stored knowledge can be reused and connected over time.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/jacob-dietle/context-os/quickstart
Any agent
npx skills add jacob-dietle/context-os --skill quickstart
Clone the repo
git clone --depth 1 https://github.com/jacob-dietle/context-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 quickstart

README.md
[![agentmods](https://agentmods.dev/badge/skills/jacob-dietle/context-os/quickstart.svg)](https://agentmods.dev/skills/jacob-dietle/context-os/quickstart)
Your own site
<a href="https://agentmods.dev/skills/jacob-dietle/context-os/quickstart"><img src="https://agentmods.dev/badge/skills/jacob-dietle/context-os/quickstart.svg" alt="Measured on agentmods" height="20"></a>
Per session 107 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,587 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. Scan, not verified.
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 $0.00107 $0.01587
Opus 5 $0.00053 $0.00794
Sonnet 5 $0.00021 $0.00317
Haiku 4.5 $0.00011 $0.00159

Measured 4d ago against content hash 1e0f2b0935f4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

quickstart scanned grade C with 2 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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

- macOS/Linux: `curl -fsSL https://install.tastematter.dev/install-context-os.sh | bash`

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- macOS/Linux: `curl -fsSL https://install.tastematter.dev/install-context-os.sh | bash`
.claude/skills/quickstart/SKILL.md · 190 lines

How it starts

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

Context OS Quickstart

Walk the user through building their first context operating system — a structured knowledge graph where AI compounds intelligence over time.

Approach

Be adaptive. Meet users where they are. Context OS is emergent architecture — it only works with real content to compound. A one-off demo transformation is meaningless.

Step 0: Assess Starting Point

FIRST, before any welcome message, check two things:

  1. Check if context-os CLI is installed: Run context-os --version. If it fails, tell the user: "The context-os CLI is required for graph queries and file heat tracking. Install it first:

    • macOS/Linux: curl -fsSL https://install.tastematter.dev/install-context-os.sh | bash
    • Windows: irm https://install.tastematter.dev/install-context-os.ps1 | iex Then start the Context OS quickstart again." Stop here if CLI is not installed.
  2. List the target directory and look for existing content: transcripts, docs, notes, raw files

If directory is empty or doesn't exist: → Go to Step 1A (Blank Slate)

If directory has content: → Go to Step 1B (Existing Content)

Step 1A: Blank Slate Flow

"Welcome to Context OS Quickstart.

I'm going to help you build a system where your AI compounds intelligence over time — no more repeating context every session.

Important: Context OS is emergent architecture. It only works when you have real content to ingest. We need YOUR transcripts, docs, notes, or emails.

Two questions:

  1. What's this context OS for?

    • GTM / Sales (deals, prospects, positioning)
    • Product (specs, decisions, technical knowledge)
    • Research (notes, papers, insights)
    • Something else?
  2. What content do you have to seed it?

    • Meeting transcripts?
    • Documents or specs?
    • Notes or emails?
    • Where are these files located?"

Wait for response. Must have content source identified before proceeding.

Step 1B: Existing Content Flow

"Welcome to Context OS Quickstart.

Read the full file on GitHub · 190 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. 4d ago First seen · 190 lines · 107 tokens per session scan C 1e0f2b0935f4

Subscribe to this mod's changes

quickstart is a skill published in the GitHub repository jacob-dietle/context-os (108 stars, last pushed 21d ago), licensed MIT. It adds 107 tokens to every session and 1,587 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens