Install
$ agentstack add skill-btspoony-mstar-harness-mstar-host Open-source listing, not yet scanned by AgentStack. Follow the source repository for install instructions.
Security review
⚠ Flagged1 finding(s); flagged for manual review. · v0.1.0 How review works →
- • Prompt-injection patterns
- • Secret / credential exfiltration
- • Dangerous shell & filesystem operations
- • Untrusted network calls
- • Known-malicious package signatures
- high Dangerous shell/eval execution.
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ● Dynamic code execution Used
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Morning Star Host Adapter
Host-specific capabilities and entry behavior for Morning Star. Process gates and invariants stay in mstar-harness-core and topic mstar-* skills.
First action
Read mstar-harness-core before this skill (even when the host injects project AGENTS.md).
Default path
- Read
mstar-harness-core - Read
mstar-host(this skill) and detect host below - Read
references/.mdfor the active host - Load role via
mstar-roles - Execute with evidence-first completion checks
Load topic skills on demand per mstar-roles (do not read every mstar-* skill by default). Cursor routing-eval (.cursor/skills/mstar-routing-eval/) is regression tooling only — not part of runtime load order.
Detect active host
Detect from session tool shapes and available commands — not from plugin markers on disk. The *-plugin/plugin.json files cannot identify the host: they all coexist in this harness source repo and in any multi-host install.
| Signal | Host | Next read | |--------|------|-----------| | subagent_type param on the Task tool (plus CreatePlan/SwitchMode when Plan mode is active) | cursor | references/cursor.md; Plan mode also references/cursor-plan-mode-bridge.md | | question tool, or task tool with subagent (singular) — no tasks[] batch | opencode | references/opencode.md | | task tool with agent / tasks[] batch, ask, hub (omp also exposes /goal; goal rule is host-agnostic per below) | omp | references/omp.md; Plan mode also references/omp-plan-mode-bridge.md | | Agent / AskUserQuestion / EnterPlanMode + AgentSwarm (Kimi-only) | kimi | references/kimi.md; Plan mode also references/kimi-plan-mode-bridge.md | | Agent / AskUserQuestion / EnterPlanMode / TodoWrite, no AgentSwarm | zcode | references/zcode.md; Plan mode also references/zcode-plan-mode-bridge.md | | /plan, /goal slash commands; Goal tools; functions.* / codex_app.* tool namespaces; tool_search; Browser plugin tools | codex | references/codex.md; Plan mode also references/_shared/plan-mode-bridge-core.md | | Still ambiguous | - | Read sections in cursor.md, opencode.md, codex.md, kimi.md, zcode.md, and omp.md that match tools you have; mstar-harness-core wins on conflict |
Order matters: check cursor → opencode → omp → kimi → zcode → codex. subagent_type (Cursor) vs subagent (OpenCode) vs agent/tasks[] (omp) is the sharpest split among the Task-based hosts.
> Engine check (when available): run mstar host detect --signals (or import { detectHost } from "@mstar-harness/engine" in a host hook) to resolve the detection table above from session tool shapes (prints the host id, or ambiguous to fall back on the table + judgment). On fail -> do not proceed; fix and re-run. Skill text below remains authoritative when the runtime is absent.
Parallel dispatch (invoke-capable hosts)
When PM dispatches N >= 2 concurrent assignees (QC tri-review, dual-track implement, etc.) and the host exposes actual invoke / Task / subagent tools, read references/parallel-dispatch.md in the dispatch round (shared with mstar-dispatch-gates). Without a callable invoke tool when dispatch is required → Blocked; Assignment Markdown alone is not dispatch.
/goal directive (host-agnostic)
Applicability is by capability, not host identity: any host that exposes a /goal command (currently Codex Goal Mode and omp; other code agents may add it later) attaches a persistent objective to the thread. Rule — always set the goal to running the complete flow to the end, never a sub-stage:
- Advancing an iteration: set the goal to complete the entire iteration flow (
iteration-start → per-plan cycles → iteration-close → PR delivery → PR merge-ready loop). Do not set a sub-stage goal (e.g. "finish Phase 1 only"). - Advancing non-iteration work (single plan / hotfix / one-off task): set the goal to complete the entire per-plan flow (
specify → clarify → plan → tasks → implement → plan QC tri + QA gate → Done). Do not set a sub-stage goal (e.g. "write the plan" or "implement one task").
Goal text is a session-level objective only: {HARNESS_DIR} / {PLAN_DIR} / status.json remain SSOT, and goal completion is not harness Done. Mirror goal success criteria into the SSOT plan; when the goal changes, update goal text and the SSOT in the same round.
Resolve loaded skill root
Docs name assets as skill **`** → scripts/… / references/…. **Resolve the loaded skill directory first** — do **not** open skills//…` from a consumer app cwd (that layout exists in the harness source / plugin package only).
| Host | Prefer | Filesystem fallback (only if the host cannot load by name) | |------|--------|--------------------------------------------------------------| | omp | skill:// / skill:/// / /skill: | Plugin package root skills// after install/link — not app cwd | | Cursor | Skill name via plugin skills | Global ~/.cursor/plugins/local/morning-star-harness/skills//; project .cursor/plugins/morning-star-harness/skills// | | Codex | Skill name via plugin | Plugin-mounted skills//; project command skills under .agents/skills// | | OpenCode | Skill name via @mstar-harness/opencode | Package-internal harness-skills// — never process.cwd()/skills/ | | Kimi / ZCode | Skill name / /skill: | Plugin mount ./skills// from the installed plugin root |
Authoring convention: mstar-skill-authoring § Skill-relative script and asset paths. Per-host URI / mount detail: references/.md.
> Engine check (when available): import resolveSkillRoot from @mstar-harness/engine in a host hook to resolve the loaded skill root per the table above (no CLI form yet). On fail -> do not proceed; fix and re-run. Skill text below remains authoritative when the runtime is absent.
Conflict order
- User explicit instructions (this turn)
- Project
AGENTS.md/CLAUDE.md mstar-harness-coreand relatedmstar-*skills- This
mstar-hostskill andreferences/*
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: btspoony
- Source: btspoony/mstar-harness
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.