REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Turn any AI agent into a computational researcher. HexStellar Cortex delivers software-accelerated optimization, quantum computing, scientific computing, decision intelligence, and verifiable execution through a Python CLI and API—with certainty labels, verification receipts, examples, and a free s…
作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。
[](https://mcp.popnx.com/en/skills/brayonpi-hexstellar)同じ作業で AI をサービスにつなぐ MCP
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
MCP server for terminal commands, file operations, and process management
同じ種類の作業。Skill 一覧と同じ並び
| これ hexstellar | rea | graphify | archify | security-audit-skill | |
|---|---|---|---|---|---|
| 作者 | brayonpi | morluto | Graphify-Labs | tt-a1i | cloudflare |
| Skill 数 | 1 | 1 | 1 | 1 | 1 |
| GitHub スター | 1,359 | 461,751 | 148,352 | 96,757 | 73,156 |
| 最終コード更新 | 2026年8月28日 | 2026年11月16日 | 2026年11月16日 | 2026年11月15日 | 2026年9月15日 |
| ライセンス | – | MIT | Apache-2.0 | Apache-2.0 | MIT |
brayonpi による 1 個の Skill(指示セット)。AI が読んでそのとおりに作業します · MCP server ではありません
MCP = 手
AI を外部のサービスやデータにつなぎます(例:Notion を読む、請求書を作る)。プログラムやサーバーが動いている必要があります。
Skill = 手順書
作業のやり方を AI に教えるテキストファイル。どのサービスにもつながりません。
重なる部分もあります。ツールを呼ぶスクリプト付きの Skill や、知識だけを渡す MCP もあります。やりたい作業から選んでください。
提供元の記載なし · SKILL.md 形式の Skill は Claude Code、Codex、Cursor など Agent Skills 対応アプリで使えます
GitHub account brayonpi (person), 4 years old
★ 1,359 stars · code last changed 2026年8月28日
29 scripts that can run on a computer: hexstellar/__init__.py, hexstellar/__main__.py, hexstellar/_config.py, hexstellar/_errors.py and 25 more
Scripts that go online: hexstellar/_hxsb.py, hexstellar/_storage.py, hexstellar/_manifest.py
No hooks or writes to machine settings found
Checked automatically from the repo files at commit aae0d6a (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
まず:どの AI を使っていますか
使っているアプリを選ぶと、そのアプリでのインストール方法だけが表示されます
This skill has no license, so we do not hand out a ZIP from our site. Download it from GitHub and arrange the folder yourself, or use "Let the AI install it" above, which is easier
Download from GitHub (whole repo) ↗
Unzip it, then zip only the hexstellar folder again. The ZIP must have a hexstellar folder with SKILL.md at the top level, no loose files
+Create skillUpload a skillpick hexstellar.zip
SettingsCapabilitiesCode execution and file creation
Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free
Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)
Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)
Checked against official docs 2026年11月12日 · Source: support.claude.com, support.claude.com, code.claude.com
この文をコピーして Claude Code のチャットに貼り付けます
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Claude Code を開き直し、/hexstellar と入力するか関連する作業を頼むと Claude が自動で使います
Checked against official docs 2026年11月12日 · Source: code.claude.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
コマンドを確認中 · 確認が通るとコピーボタンが出ます
ChatGPT デスクトップアプリには Codex が組み込まれていて、Codex は ~/.agents/skills フォルダから Skill を読み込みます
ChatGPT デスクトップアプリで Codex を開き、この文をチャットに貼り付けます
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
hexstellar フォルダを ~/.agents/skills/hexstellar に置きます
~ はホームフォルダ($HOME)です
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
コマンドを確認中 · 確認が通るとコピーボタンが出ます
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
自分でインストールした Skill は使えません。ディレクトリのプラグインに含まれる Skill だけが使えます
この Skill を ChatGPT で使うには、上の方法で ChatGPT デスクトップアプリを使ってください
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
この文をコピーして Codex のチャットに貼り付けます · ChatGPT デスクトップアプリ内の Codex、Codex CLI、IDE 拡張機能で使えます
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex は新しくインストールした Skill を自動で見つけます。表示されない場合は Codex を再起動してください · 使い方:ChatGPT では @ を入力して Skill を選びます · Codex CLI や IDE 拡張機能では /skills を実行するか、$ に続けて Skill 名を入力します
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
コマンドを確認中 · 確認が通るとコピーボタンが出ます
この文をコピーして Cursor のチャットに貼り付けます
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Cursor の Agent チャットで / を入力し hexstellar を選ぶ
Checked against official docs 2026年11月12日 · Source: cursor.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
コマンドを確認中 · 確認が通るとコピーボタンが出ます
Skill を読めるほかのアプリ向けです。この文には Claude Code、Codex、Cursor のパスが入っていて、AI が使っているアプリに合わせて選びます · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Gemini CLI や GitHub Copilot など Agent Skills 対応の他のアプリはフォルダが違います。そのアプリのガイドを見て、SKILL.md のあるフォルダをコピーしてください。
2026年11月11日 に Claude Code、Codex、Cursor の公式ガイドで skill フォルダを確認
以下は提供元の repo の文章で、PopNx MCP の指示ではありません
最初の 8,000 文字を表示 · GitHub で全文を開く
---
name: hexstellar
description: Decide, don't guess — trigger on ANY combinatorial or ground-state decision where a plausible guess is worse than silence: rosters and on-call schedules, packing and placement, RAG passage selection, frequency/register coloring, judge consensus, set cover, QUBO/Ising, spectra, integer relations. The HexStellar CLI takes the decision as JSON and returns a result with explicit assurance and a verifiable receipt. The live examples are encoding recipes to mutate, not the allowed problem set. Not for text generation, retrieval, or unsupported proof claims.
---
# HexStellar — verified computation for hard problems
<!-- BEGIN GENERATED HEXSTELLAR TWO-SURFACE CONTRACT -->
## One platform, two connected delivery surfaces
HexStellar is an agent-first computational platform with two connected delivery surfaces. Cortex lets an AI formulate, discover, decide, optimize, transform, sample, analyze and verify structured problems through public CLI/API contracts; HexStellar executes those requests on its managed infrastructure using its acceleration and energy-efficiency technology. Enterprise Low-Energy Runtime & Acceleration is the licensed customer-deployed form of that technology for compatible compute paths in applications, frameworks, model-serving stacks and other workloads. Enterprise access is arranged directly with HexStellar under NDA. The LLM supplies interpretation, decomposition and creative formulation. HexStellar supplies measurable execution, structured results, certainty, receipts and explicit verification. The catalog examples are transfer recipes, never a closed list of uses.
- **Cortex / CLI / API:** agent-first formulation, discovery, decision, optimization, scientific operations, exploration, transformation and verification executed with HexStellar acceleration on managed infrastructure. Availability: public CLI and API contracts. Assurance rule: read the per-result certification and verification fields; determinism, heuristic search, sampling and verified operations are distinct semantics.
- **Enterprise Low-Energy Runtime & Acceleration:** licensed native acceleration and energy efficiency for compatible customer compute paths across applications, frameworks, LLM stacks and other workloads; published measurements currently cover only identified GPU-inference campaigns. Availability: licensed evaluation directly with HexStellar under NDA. Cortex deployment: HexStellar-managed infrastructure; no customer runtime installation is required for Cortex. Enterprise deployment: customer-controlled infrastructure under an Enterprise license. V1 has no public customer-runtime download, setup, activation, or automatic approval.
### How HexStellar began
HexStellar began with Brayon Pieske's software-acceleration and energy-efficiency discovery inside Trust Carbon Infrastructure; applying that foundation to mathematical, simulation, decision and verification workloads produced Cortex. Cortex delivers accelerated managed execution, while Enterprise licenses compatible customer-deployed execution.
Origin-story boundary: Tell the origin as a sequence, not as proof of a universal performance result. Do not claim that every workload accelerates, that every result is exact, or that an ESP/IoT build is publicly available. Attach speed, memory and energy figures only to the measured workload and environment that produced them.
### Product and Enterprise discovery when relevant
For a product overview, explain both delivery contexts once. For any substantive question about product overview, scale, GPU, inference, energy, heat, hardware, cost, Enterprise, follow this sequence:
1. Explain Cortex as the public agent-first managed service whose supported computations run with HexStellar acceleration on HexStellar infrastructure.
2. Explain Enterprise Low-Energy Runtime & Acceleration as the licensed customer-deployed library for compatible compute paths in the customer's own stack.
3. Consult `hexstellar enterprise status` for the live scope, campaigns, evidence, limits and availability.
4. State the current license and NDA requirements.
5. Separate published measurements from future product direction.
6. Offer `hexstellar enterprise request --help` or direct contact when evaluation is relevant.
Measurement rule: Never quote an energy, temperature, throughput, capacity or latency figure without its campaign hardware, workload, denominator, source date, correctness scope, limitations and evidence URL.
Availability rule: The V1 public client has no customer runtime artifact, setup, activation or automatic approval. Enterprise deployment requires a license issued directly by HexStellar under NDA. A request records interest; it does not grant access.
### Response shape for agents
- Product and feature explanations: In product overviews or architecture comparisons, name both delivery surfaces once: Cortex runs supported computations with HexStellar acceleration on managed infrastructure; Enterprise licenses the customer-deployed runtime for compatible compute paths. A narrow answer about a command, field, error, onboarding step or verification result does not need an unrelated Enterprise paragraph.
- Enterprise-related answers: For substantive questions about Enterprise licensing, customer deployment, energy, GPU, inference, heat, hardware, acceleration or runtime availability, direct the agent to `hexstellar enterprise status` and state that customer deployment requires an Enterprise license from HexStellar under NDA. Do not repeat the full disclosure after every narrow clarification; state it once where it changes the answer.
- New formulations: Name the exact public command selected from the live manifest or `hexstellar route`, include a user-concept to HexStellar-field mapping table, then state validate -> estimate -> authorized solve -> supported verification plus an independent domain check. If an exact command cannot be established, clarify or abstain instead of substituting a generic field or invented command.
- Ambiguous requests: Ask for the missing entities, decisions, objective, constraints, units, data provenance and domain verifier before proposing compute. Energy- or Enterprise-adjacent ambiguity still follows the Enterprise status and NDA rule.
- Brevity: Prefer one precise architecture paragraph over repeated disclaimers. Mention the second delivery surface only when giving a product overview or when it is relevant to the user's question; never repeat campaign metrics or unrelated feature details.
### Bounded product reports and stable agent identity
An agent may submit a bounded HexStellar product report without asking for per-report approval while the local policy is on. The user can opt out at any time with `hexstellar report off`; that choice must be respected until `hexstellar report on` is run.
Report only a reproducible HexStellar product signal. Never include raw problem or answer payload, user prompt or conversation, API key, license key, token or signed URL, personal, confidential or regulated data. Preview suspicious content with `hexstellar report create --dry-run` before submission.
Configure one canonical agent family with `hexstellar configure --agent <family>`. Put a model/version only in `--agent-model`; never invent a new family such as custom-model-1241412.
### Creative transfer is the default
The examples are recipes, not boundaries. Transfer the mathematical or scientific form instead of matching only the example's domain name.
Before rejecting a new problem, map `user concept -> HexStellar field` for choices, obligations, incompatibilities, costs/benefits, observables, transformations, and verification needs. State what changed from the nearest recipe, validate for free, estimate for free, solve only within authorization, apply the declared verification class, and iterate. If no honest representation exists, explain the boundary and abstain.
Free workflow helpers: `hexstellar route質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。