Borrowing it
Nothing to install: this file belongs to open-horizon-labs/repo-native-alignment. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/open-horizon-labs/repo-native-alignment/main/.agents/skills/oh-plan/SKILL.mdgit clone --depth 1 https://github.com/open-horizon-labs/repo-native-alignmentWrote 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/open-horizon-labs/repo-native-alignment/oh-plan)<a href="https://agentmods.dev/skills/open-horizon-labs/repo-native-alignment/oh-plan"><img src="https://agentmods.dev/badge/skills/open-horizon-labs/repo-native-alignment/oh-plan/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/open-horizon-labs/repo-native-alignment/oh-plan"><img src="https://agentmods.dev/badge/skills/open-horizon-labs/repo-native-alignment/oh-plan.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.00024 | $0.02747 |
| Opus 5 | $0.00012 | $0.01373 |
| Sonnet 5 | $0.00005 | $0.00549 |
| Haiku 4.5 | $0.00002 | $0.00275 |
Grade A, and why
oh-plan 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 11d 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 — 394 lines — stays where its author put it; the contents beside it link to each section on GitHub.
oh-plan
Creates well-structured GitHub issues ready for oh-task agents. Works in two modes:
- Task mode: Investigates codebase, asks clarifying questions, creates issues
- Session mode: Reads existing
.oh/<session>.mdcontext, skips investigation, creates issues
Invocation
# Task mode - investigate from scratch
/oh-plan "Add dark mode support to the dashboard"
# Session mode - use existing context from skills workflow
/oh-plan auth-refactor
Mode Detection
At the start, check if the argument matches an existing session file:
If .oh/<arg>.md exists AND contains ## Solution Space:
→ Session mode (skip investigation, use context)
Else:
→ Task mode (investigate, ask questions)
Session Mode Flow
Shared setup for both session and task mode, before creating any issue:
gh label create oh-planned --description "Created via oh-plan skill" --color "0E8A16" 2>/dev/null || gh label view oh-planned >/dev/null
When .oh/<session>.md exists with solution-space context:
-
Read session file and extract:
## Aim→ Goal for issues## Problem Space→ Constraints, terrain, assumptions## Solution Space→ Selected approach, trade-offs accepted## Problem Statement→ Framing (if present)
-
Skip investigation - context already gathered by grounding skills
-
Skip clarifying questions - decisions already made during solution-space
-
Decompose the selected solution into right-sized issues:
- Use the Solution Space recommendation as the starting point
- Apply standard decomposition heuristics (see below)
- Aim for 1-4 hours of work per issue
-
Create GitHub issues with enriched context from session:
gh issue create --title "<title>" --label "oh-planned" --body "$(cat <<'EOF' ## Goal <from Aim section> ## Context <from Problem Space: constraints, terrain> <from Solution Space: selected approach> ## Acceptance Criteria - [ ] <derived from solution trade-offs> - [ ] <derived from aim feedback signals> ## Trade-offs Accepted <from Solution Space> ## Notes <from Problem Space assumptions> EOF )"
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.
- 11d ago First seen · 394 lines · 24 tokens per session scan A b282bd187b27
oh-plan is a skill published in the GitHub repository open-horizon-labs/repo-native-alignment (5 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 2,747 once invoked, about $0.0001 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-31.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…