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/solution-space/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/solution-space)<a href="https://agentmods.dev/skills/open-horizon-labs/repo-native-alignment/solution-space"><img src="https://agentmods.dev/badge/skills/open-horizon-labs/repo-native-alignment/solution-space/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/solution-space"><img src="https://agentmods.dev/badge/skills/open-horizon-labs/repo-native-alignment/solution-space.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.00034 | $0.02876 |
| Opus 5 | $0.00017 | $0.01438 |
| Sonnet 5 | $0.00007 | $0.00575 |
| Haiku 4.5 | $0.00003 | $0.00288 |
Grade A, and why
solution-space 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 — 400 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/solution-space
Explore candidate solutions before committing to implementation. The trap is defending the first workable idea.
Solution Space sits between Problem Statement and Implementation. You have the problem framed; now map the approaches before picking one.
When to Use
Invoke /solution-space when:
- Problem is understood - You have a clear problem statement
- Multiple approaches seem viable - Not obvious which path is best
- You're about to start coding - Pause and explore before committing
- Patches keep accumulating - Third config flag for the same bug
- You feel attached to your first idea - That's the warning sign
Do not use when: You're still clarifying the problem. Use /problem-statement first. Solution Space assumes the problem is framed.
The Local Maximum Trap
"The hardest part of design has never been coming up with ideas. It is letting go of the first workable idea to look for better ones."
Exploration is cheap. The failure mode is defending the first solution that works.
Signs you're stuck on a local maximum:
- First solution considered is the only solution considered
- You're explaining why alternatives won't work before trying them
- You're acting as a crafter (defending) rather than an editor (filtering)
- Implementation details discussed before approaches compared
The Escalation Ladder
Not all problems need redesigns. The ladder helps you find the right altitude.
Level 1: Band-Aid Fix
Don't default to this. Patch the symptom.
- Fine under deadline pressure
- Toxic as habit
- Signal: "This will break again"
Example: Add a null check. Catch the exception. Hardcode the edge case.
Level 2: Local Optimum
Better, but limited. Optimize within current assumptions.
- Classic refactor trap
- Improves what exists without questioning it
- Signal: "This is cleaner but the same shape"
Example: Extract a method. Add a parameter. Refactor for readability.
Level 3: Reframe
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 · 400 lines · 34 tokens per session scan A 929234a4d843
solution-space is a skill published in the GitHub repository open-horizon-labs/repo-native-alignment (5 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 2,876 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…