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/arch3rpro/ark-space/orchestratornpx skills add arch3rPro/ark-space --skill orchestratorgit clone --depth 1 https://github.com/arch3rPro/ark-spaceWrote 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/arch3rpro/ark-space/orchestrator)<a href="https://agentmods.dev/skills/arch3rpro/ark-space/orchestrator"><img src="https://agentmods.dev/badge/skills/arch3rpro/ark-space/orchestrator.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.00028 | $0.01675 |
| Opus 5 | $0.00014 | $0.00838 |
| Sonnet 5 | $0.00006 | $0.00335 |
| Haiku 4.5 | $0.00003 | $0.00168 |
Grade A, and why
orchestrator 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 4d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator
Route work before expanding process. When invoked as ark-space:orchestrator, act as the ArkSpace entrypoint, not as a generic host assistant.
Use the lightest role and workflow that can safely complete the task. Route first by user intent, then by artifact type, then by risk. Escalate only when the task crosses domains, changes shared structure, requires long-term maintainability, or has unclear success criteria.
ArkSpace runs inside the host's agent loop. Your task is to keep that loop focused: choose the role, workflow, skill, provider capability, and readiness check that make the requested work executable.
Entry Contract
ArkSpace work runs through ArkSpace roles, workflows, skills, and registries. Host-native capabilities are not ArkSpace providers.
For any capability represented by a provider registry, use that registry as the authority before execution:
- Choose the role from
roles/or the default route table. - Choose the capability, such as
web_search,web_fetch,web_map,web_crawl,structured_extract,web_interact,web_monitor,deep_research,code_context, orrelated_pages. - Read the matching provider registry, such as
registry/search-providers.yaml. - Select the highest-priority active provider that matches the role, capability, and privacy requirements.
- Run the provider's
checkCommandwhen configuration state matters. - If a selected provider requires configuration and the check fails, route to
provider-managersetup and stop before producing capability results. - Continue only after the provider check succeeds, another registered provider passes the same checks, or the user explicitly asks to bypass ArkSpace provider routing.
- When stopped for missing configuration, present the missing capability, the setup command, and the value needed from the user before offering alternatives. If the user declines, defers, or cannot complete setup and still wants results, ask whether to continue with a clearly labeled non-ArkSpace fallback.
- Report the strongest readiness level proven by evidence: source-ready, package-ready, installed-host-ready, provider-ready, or live-provider-ready.
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.
- 4d ago First seen · 119 lines · 28 tokens per session scan A 7c1fb6ff7260
orchestrator is a skill published in the GitHub repository arch3rPro/ark-space (2 stars, last pushed 9d ago), licensed MIT. It adds 28 tokens to every session and 1,675 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
invest
First-time fork users: run the invest-setup skill first to initialize. The main flow lives in this skill (the AI agent uses the CLI/MCP to view the portfolio / run the committee / replay decision history). The Web GUI has been retired (2026-07) — every capability is exposed via CLI subcommands / MCP tools. The backend…
invest-setup
First-time openInvest installation and onboarding. ONLY use when user explicitly says "set up invest" / "init invest" / "帮我初始化 invest", OR when invest skill's doctor returns status="needssetup". NOT for daily usage — once onboarding is done, the invest skill takes over (portfolio viewing, committee analysis, buy/sell…
okf-frontmatter
Maintain openInvest's docs (docs/wiki chapters + docs/wiki/adr) under Google's Open Knowledge Format (OKF). Two jobs. (1) Teach agents to maintain docs the OKF way — every doc carries a small YAML frontmatter block as the single source of truth (type, title, tags, intent, schemasource, documents); schema details link…
invest-backup
Back up / restore openInvest's local state — memory/ (holdings, strategy, user profile, committee records, dream logs) + db/ (trade ledger, job run history, market-data cache) + .env (SMTP/API credentials) + userprofile.json. All of this data is .gitignore'd with no historical versions in git, so a single accidental…
openehr-assistant
This skill should be used when a conversation touches openEHR outside a task owned by a dedicated skill — e.g. "what is an archetype?", "how do openEHR templates work?", "which composition category fits this data?", "find me a guide on X", "where do I start with openEHR modeling?" — or names openEHR concepts (ADL…
template-authoring
This skill should be used when the user asks to "create a template", "design a template", "constrain archetypes into a template", "review a template", "categorise a dataset with CGEM", "should this be persistent, episodic or event?", "split this form across compositions", "sketch a template from this form / which…