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-runtimegit 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-runtime)<a href="https://agentmods.dev/skills/pedroknigge/arkgate/ark-runtime"><img src="https://agentmods.dev/badge/skills/pedroknigge/arkgate/ark-runtime/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-runtime"><img src="https://agentmods.dev/badge/skills/pedroknigge/arkgate/ark-runtime.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.02951 |
| Opus 5.5 | $0.00010 | $0.01180 |
| Sonnet 5.5 | $0.00005 | $0.00590 |
| Haiku 4.5 | $0.00003 | $0.00295 |
Grade A, and why
ark-runtime 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 24d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ark-runtime — Evaluate and wire ArkRun (experimental opt-in)
Contener · Guiar · Ordenar. In plain words: contain the write, guide the next step, order leftover mess. This door is Guiar: wire the optional runtime so work keeps moving. Skills never enforce — CLI / hooks / CI do.
The ArkRun kernel (arkgate/runtime) is currently experimental. It is not required
for ArkGate enforcement and is not production durability. Use this skill when the user wants
to evaluate or wire the kernel. This skill never enforces — the write / CI / ESLint plane
does when the arkRun extra is on. Do not invent /ark-run. @arkgate/runtime is deprecated.
When: evaluate a hand-rolled bus / outbox / saga / projection / policy / Nest adapter against
the kernel, or wire an extra that is already on (kernel root, declarations, transport).
Not when: session 0 / extra not chosen (/ark-adopt); one new file (/ark-place); skip-violation
grind (/ark-autopilot); wire the order plane (/ark-order).
When / not when
Use /ark-runtime when… |
Do not use it when… |
|---|---|
| Wire one ArkRun candidate after the extra is on | Extra not chosen → /ark-adopt |
| Evaluate a hand-rolled bus / outbox / saga | New kernel-managed file only → /ark-place |
| Declarations / transport / Nest adapter | Skip cluster grind → /ark-autopilot; one order-plane candidate → /ark-order |
Extra vs kernel (mandatory)
| Piece | What it is | What it is not |
|---|---|---|
ArkRun extra (arkRun on ark.config.json, schema 1.2+) |
Gate contract: kernel usage + complete declarations | A score; Layers / ArkRules replacement; merge teeth while advisory |
Kernel arkgate/runtime |
Kernel you construct with createStrictArkKernel (one instance per call) |
A process-wide getKernel(); shipped cloud broker SDKs; production durability |
Absence of the extra is silent — Layers and ArkRules verdicts stay identical. Compact
doctor names ArkRun only when the extra is on (experimental, in-memory, not Postgres;
/ark-runtime when residual remains). Doctor / status arkRun is always notAScore.
Never invent 0–10 scores or pass/fail from this skill.
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.
- 24d ago Changed · +5 lines 7390a7fd96ab
- 27d ago Changed · +2 lines bfc5f680011f
- 1mo ago Changed · +2 lines 9b5b35493938
- 1mo ago Changed · +13 lines 873656ede500
- 1mo ago Changed · +3 lines 0e1d17c261fa
- 1mo ago First seen · 167 lines · 25 tokens per session scan A cd95a69e2b45
ark-runtime is a skill published in the GitHub repository pedroknigge/arkgate (1 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 2,951 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-08-31.
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…
Architecture Change Communication
Ensure architecture updates document affected stakeholders, notification plan, and deprecation/retirement signals to keep knowledge aligned.