Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add mishahanin/heading-os-marketplace/plugin install heading-coreWrote 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/mishahanin/heading-os-marketplace/prime)<a href="https://agentmods.dev/skills/mishahanin/heading-os-marketplace/prime"><img src="https://agentmods.dev/badge/skills/mishahanin/heading-os-marketplace/prime/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.
<a href="https://agentmods.dev/skills/mishahanin/heading-os-marketplace/prime"><img src="https://agentmods.dev/badge/skills/mishahanin/heading-os-marketplace/prime.svg" alt="Reviewed on agentmods" width="80" 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.00078 | $0.03481 |
| Opus 5 | $0.00039 | $0.01741 |
| Sonnet 5 | $0.00016 | $0.00696 |
| Haiku 4.5 | $0.00008 | $0.00348 |
Grade A, and why
prime 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 7d 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.
This is a copy
94% identical to prime — 16 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prime
Initialize the session. Load full context. Surface priorities. Recommend today's agents.
Read
First, read .workspace-identity.json to determine workspace type.
CLAUDE.md is already auto-loaded by the Claude Code harness (visible in the system prompt's claudeMd block) - do NOT re-read it.
Load the following files in this order (paths depend on workspace type):
CEO workspace (flat paths):
context/personal-info.md- who Misha iscontext/business-info.md- 31C organization and ODUN.ONEcontext/strategy.md- strategic priorities and arccontext/current-data.md- current metrics, milestones, active workstreamscontext/people.md- read only the "Top 10 Active Contacts (summary)" section. Full file remains available - Readcontext/people.mdwhen a specific named contact requires deeper context.context/pipeline.md- active deals and investor conversationsreference/workspace-overview.md- read only the H1 + "## Index" section. Defer the per-section detail to lazy-read when a specific tool, script, or system needs deeper context.datastore/INDEX.md- read only the H1 + "## Top-Level Structure (summary)" section. Defer the per-document tables to lazy-read when a specific fact needs validating.
Exec workspace (shared content under corporate/, personal under personal/):
personal/context/personal-info.md- who the exec iscorporate/context/business-info.md- 31C organization and ODUN.ONEcorporate/context/strategy.md- strategic priorities and arccorporate/context/current-data.md- current metrics, milestones, active workstreamscorporate/context/people.md- read only the "Top 10 Active Contacts (summary)" section when present. Full file remains available for lazy-read.corporate/context/pipeline.md- active deals and investor conversationscorporate/datastore/INDEX.md- read only the H1 + "## Top-Level Structure (summary)" section when present.
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.
- 7d ago Changed · +1 lines f050e25eb746
- 12d ago First seen · 216 lines · 78 tokens per session scan A 21b748ea105e
prime is a skill published in the GitHub repository mishahanin/heading-os-marketplace (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 78 tokens to every session and 3,481 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to prime, differing in 16 lines, and is treated as a copy.
Other skills, from other repositories
alive-bundle
Create, manage, and graduate bundles -- the unit of focused work within a walnut.
pm-engine
Interface with the PM-ENGINE-MEMORY file — the operator's accumulated PM tacit knowledge database. Enables agents to reference, search, and apply TK (Tacit Knowledge) entries, and supports TK extraction from experience (--mode extract), TK querying and referencing (--mode query), and TK-to-instruction conversion…
consolidate
Audit knowledge directories (.memory/, docs/, staging/, archive/) and Claude Code auto memory for stale, misplaced, or duplicated content. Generates an editable cleanup plan file, then executes approved actions after review. Use when: periodic knowledge cleanup, after project milestones, files feel scattered or…
advisor-operator
Use when assessing feasibility, building an implementation plan, estimating timelines, or planning resource allocation. Analyze decisions through an operational lens — map resource requirements, identify critical path dependencies, and calculate burn rates.
working
Manage ephemeral .memory/ conversation state across multi-day sessions. Checkpoint todos, decisions, and questions; promote artifacts to permanent knowledge; clean up after promotion. Use when: the user says 'checkpoint', 'save working memory', 'promote working memory', 'clean up memory', wants to persist conversation…
briefing
Assembles a session context briefing from your configured issue tracker, recent git history, and active work signals. Use when: starting a new session, resuming after a break, user says 'catch me up', 'what was I working on', 'where did I leave off', context recovery after compaction, or user asks for project…