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 skills add pedroknigge/arkgate --skill ark-ordergit clone --depth 1 https://github.com/pedroknigge/arkgateWrote 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/pedroknigge/arkgate/ark-order)<a href="https://agentmods.dev/skills/pedroknigge/arkgate/ark-order"><img src="https://agentmods.dev/badge/skills/pedroknigge/arkgate/ark-order/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/pedroknigge/arkgate/ark-order"><img src="https://agentmods.dev/badge/skills/pedroknigge/arkgate/ark-order.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.00025 | $0.03140 |
| Opus 5.5 | $0.00010 | $0.01256 |
| Sonnet 5.5 | $0.00005 | $0.00628 |
| Haiku 4.5 | $0.00003 | $0.00314 |
Grade A, and why
ark-order 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 16d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ark-order — Evaluate and wire ArkOrder (optional)
Contener · Guiar · Ordenar. In plain words: contain the write, guide the next
step, order leftover mess. This door is Ordenar: the extra for the few big product
choices (billing plan, not seat counts). Ordering leftover folders is /ark-explore
then /ark-autopilot. Skills never enforce — CLI / hooks / CI do.
Layers stop a bad import. ArkOrder stops rewriting a big product choice as if it were a seat count. Change those choices through a valve, not a generic update.
The ArkOrder extra (arkgate/order) is optional. It is not required for
ArkGate enforcement and is not production durability. Use this skill when the
user wants to evaluate or wire the extra. This skill never enforces. Do not
invent /ark-run. @arkgate/order is not a package — import arkgate/order from
the same arkgate tarball.
When: evaluate a hand-rolled “PATCH the plan like a seat count” / generic update
of a slow product choice, or wire an extra that is already on (plane root, named
keys, valve).
Not when: session 0 / extra not chosen (/ark-adopt); one new file (/ark-place);
skip-violation grind (/ark-autopilot); wire the runtime kernel (/ark-runtime).
When / not when
Use /ark-order when… |
Do not use it when… |
|---|---|
| Wire one ArkOrder candidate after the extra is on | Extra not chosen → /ark-adopt |
| Evaluate a generic update of a named product choice | New plane-root file only → /ark-place |
Valve: first release(), later proposeRelease then apply |
Skip cluster grind → /ark-autopilot; one kernel candidate → /ark-runtime |
Contener · Guiar · Ordenar
| Star | This door | Hand off |
|---|---|---|
| Contener | /ark-adopt path · /ark-place new file · /ark-upgrade pin |
Map → /ark-explore · apply → /ark-autopilot |
| Guiar | /ark-explore map · /ark-autopilot apply · /ark-runtime wire ArkRun · /ark-explain tour · /ark-coverage fitness |
Session 0 → /ark-adopt · this door for the big-choice plane |
| Ordenar | This skill — wire ArkOrder | Extra off → /ark-adopt · new plane-root file → /ark-place · skip grind → /ark-autopilot |
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.
- 16d ago Changed · +2 lines 8641e9dfb791
- 19d ago Changed · +2 lines 902a1dac5679
- 1mo ago First seen · 201 lines · 25 tokens per session scan A 3989c78bc577
ark-order is a skill published in the GitHub repository pedroknigge/arkgate (1 stars, last pushed 2d ago), licensed MIT. It adds 25 tokens to every session and 3,140 once invoked, about $0.0001 per session on Opus 5.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-09-07.
Other skills, from other repositories
architecture-patterns
Software architecture patterns and best practices.
architecture-patterns
Software architecture patterns and best practices.
architecture-paradigm-event-driven
Applies event-driven async messaging to decouple producers and consumers. Use when designing real-time or multi-subscriber systems needing loose coupling.
architecture-paradigm-serverless
Applies serverless FaaS patterns for event-driven workloads. Use when designing bursty workloads with minimal infrastructure and pay-per-execution cost model.
data-mesh-expert
Expert-level data mesh architecture, domain-oriented ownership, data products, federated governance, and self-serve platforms. Use when the user mentions architecture, domain driven, data products, governance, or platform, or when the task involves Data Mesh Principles, Domain-Oriented Data Ownership, Data as a…
code-review-architecture
Architecture-focused code review covering hexagonal boundary violations, DDD anti-patterns, CQRS misuse, and microservices coupling issues. Applied in addition to the language-specific review skill when architecture markers are detected. Invoked when reviewing hexagonal architectures, DDD patterns, or microservices…