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 agentmods add skills/mishahanin/heading-os/alignnpx skills add mishahanin/heading-os --skill aligngit 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/align)<a href="https://agentmods.dev/skills/mishahanin/heading-os/align"><img src="https://agentmods.dev/badge/skills/mishahanin/heading-os/align.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 | $0.00082 | $0.02533 |
| Opus 5 | $0.00041 | $0.01267 |
| Sonnet 5 | $0.00016 | $0.00507 |
| Haiku 4.5 | $0.00008 | $0.00253 |
Grade A, and why
align 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 5d 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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/align - Force N numbered clarifying questions before doing any work
Manual escalation lever above the default prompt-refinement.md rule. When
the user invokes /align N they are explicitly summoning a clarification
gate with exactly N numbered + lettered questions, each carrying a single
committed recommendation. Single-shot per invocation - after Phase 3
approval the skill exits and normal posture resumes.
Design spec: docs/superpowers/specs/2026-05-13-align-skill-design.md (data overlay: .heading-os-data/docs/superpowers/specs/2026-05-13-align-skill-design.md).
Phase 1 - Pre-flight + target identification
Three sub-steps, all silent on success.
1.1 Parse and validate N
Read $ARGUMENTS:
-
Empty ->
N = 5(default) -
Integer string
"1"through"10"->N = int(arg) -
Anything else (
"0","100","abc","5.5","-3") -> abort with the single-line error and stop. The error is the entire output:/align expects N between 1 and 10. Got: {arg}. Try `/align 5`.
1.2 Detect CEO vs exec context
One Glob call to set the recommendation label:
Glob("reference/misha-voice.md")
- Match found ->
voice_mode = "ceo", label =Моя рекомендация. Bilingual EN/RU per the user's preceding message language. - No match ->
voice_mode = "exec", label =My recommendation. English-only.
The voice_mode flag controls only the label string, not the conversation language. Conversation language always matches the user's last message.
1.3 Identify the substantive target request
Walk back through conversation context (in-LLM, no tool call) to find the
latest substantive user turn preceding the /align invocation. Rules:
- Skip the
/aligninvocation itself. - Skip bare command words (
ok,yes,approved,go,proceed,thanks). - Skip prior /align answer lines that look like
1a, 2c, 3 - custom: .... - Accept the first prior user turn containing an actionable request - typically the longest recent turn, often with a question, instruction verb, or pasted context.
What ships with it
2 files 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.
- 5d ago First seen · 267 lines · 82 tokens per session scan A f4cc438a8acc
align is a skill published in the GitHub repository mishahanin/heading-os (11 stars, last pushed today), licensed Apache-2.0. It adds 82 tokens to every session and 2,533 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
duckduckgo-search
Free keyless web, news, and image search via ddgs.
mcporter
List, auth, and call MCP servers/tools from the terminal.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.