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.5 | $0.00031 | $0.01392 |
| Sonnet 5.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 1mo 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 — 59 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.
- 1mo ago Changed · +1 lines f050e25eb746
- 2mo 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 1mo ago), licensed Apache-2.0. It adds 78 tokens to every session and 3,481 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to prime, differing in 59 lines, and is treated as a copy.
Other skills, from other repositories
handoff
Write a short handoff note for the next chat or a teammate, with what is done, what is open, what comes next and what was rejected and why. Saves it to project memory so the next chat sees it at the start, and prints it so it can be pasted into a message or a pull request. Use when the user ends a piece of work…
wenlan-handoff
End a work session. Stores durable captures, writes a narrative session log, and automatically applies typed item-level deltas to the current Space Brief. Invoked as /wenlan-handoff.
alive-bundle
Create, manage, and graduate bundles -- the unit of focused work within a walnut.
handoff
End a work session. Stores durable captures, writes a narrative session log, and automatically applies typed item-level deltas to the current Space Brief. Invoked as /handoff.
scout-ask
Use when the working directory is a Scout vault (it has knowledge-base/ and action-items/) and the user asks about the state of a project, initiative, person, decision, meeting or open thread ("where are we on X", "what's going on with Y", "who is Z", "what's on my plate"), or what Scout knows about a topic. Do not…
brief
Read the current Space-owned project Brief from Wenlan. With an optional topic, appends separately labeled related context from the same Space. Invoked as /brief [topic] when resuming work or asking to catch up.