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 mishahanin/heading-os --skill tribe-messagegit clone --depth 1 https://github.com/mishahanin/heading-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/mishahanin/heading-os/tribe-message)<a href="https://agentmods.dev/skills/mishahanin/heading-os/tribe-message"><img src="https://agentmods.dev/badge/skills/mishahanin/heading-os/tribe-message/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/tribe-message"><img src="https://agentmods.dev/badge/skills/mishahanin/heading-os/tribe-message.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.00101 | $0.00857 |
| Opus 5 | $0.00051 | $0.00428 |
| Sonnet 5 | $0.00020 | $0.00171 |
| Haiku 4.5 | $0.00010 | $0.00086 |
Grade A, and why
tribe-message 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 9d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tribe Message
Draft a message from Misha to the 31C Tribe. Can be sent any day - not limited to Mondays.
Variables
topic: [What is this message about? Provide the key point or theme] sea_state: [Optional - external conditions if relevant] crunch: yes | no [Is this a Crunch Mode message? Default: no] highlights: [Optional - milestones, wins, or developments to acknowledge] principle: [Optional - which of the Five Core Principles to connect to]
Instructions
Before drafting, read:
reference/misha-voice.md- Voice guide, especially Tribe Communications sectionoutputs/operations/workspace/31c-operational-state-model.md- Operational vocabulary and Five Core Principlescontext/current-data.md- Recent milestones and active workstreams
Draft a Tribe message that:
- Gets to the point fast - the Tribe reads on phones between time zones
- States the topic clearly and directly
- Connects to the operational context when relevant (sea state, heading, principle)
- If Crunch Mode: declares it, explains what it means, sets expectations
- Closes warmly but briefly - the captain's voice, not a corporate memo
- Voss layer: Apply per
.claude/rules/voss.md. For Tribe messages: label the Tribe's emotional state before the ask, invite ownership with calibrated questions rather than top-down directives. Full framework:reference/voss-negotiation.md.
Tone: Speak to 50+ experienced professionals. Direct, warm, authoritative. Never condescending. Never cheerleading. Never "Amazing work everyone!"
Length: 100-250 words. Shorter is better. Say what needs to be said and stop.
Message Types
This skill handles any Tribe communication:
- Weekly updates (sea state + heading)
- Policy or culture messages
- Milestone announcements
- Pre-event or post-event messages
- Operational updates
- Crunch Mode declarations
NEVER
- "Team" / "family" / "crew" - always "Tribe"
- "Let's give it 110%!"
- "We're all in this together"
- Military references
- Generic motivation language
- Em-dashes - use hyphens only
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.
- 9d ago First seen · 90 lines · 101 tokens per session scan A cfc9af94b520
tribe-message is a skill published in the GitHub repository mishahanin/heading-os (11 stars, last pushed 3d ago), licensed Apache-2.0. It adds 101 tokens to every session and 857 once invoked, about $0.0005 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
sdlc-review
Review Kanban handoffs and route verified outcomes.
meeting-action-items
Turn meeting notes into cited decisions, owners, tickets.
linear-tickets
Create or update high-quality Linear tickets while preserving the originating report, diagnostic links, attachments, and reporter/requester attribution. Read this whenever someone asks to create, recreate, or update a Linear issue.
shogun-agent-status
A skill that shows whether the agents in a multi-agent Japanese feudal-themed team are working, waiting, missing, or assigned tasks. It combines terminal session status, task files, and unread messages.
design-inventory
Use to run the Claude Design to ClosedLoop pipeline against the current web-ui. Stage A inventories a design export zip into schema-validated findings (typed design units - screens, regions like nav bars, standalone components like a chat dialog; UX and behavioral changes; Storybook component reuse mapping; token…
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.