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/pedroknigge/arkgate/ark-runtimenpx 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.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.00025 | $0.02547 |
| Opus 5 | $0.00013 | $0.01273 |
| Sonnet 5 | $0.00005 | $0.00509 |
| Haiku 4.5 | $0.00003 | $0.00255 |
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 3d 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 — 167 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)
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 / leftover /ark-fix).
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. Doctor / status
arkRun is always notAScore. Never invent 0–10 scores or pass/fail from this skill.
Improvement compass note
This skill is experimental runtime only. Do not treat runtime adoption as residual on the
resilience lens unless the user explicitly opts into the experimental kernel. Prefer doctor compass
for static architecture residual; hand static residual to /ark-explore / /ark-autopilot.
Doctor arkRun residual is a finding-id count (ARKRUN_*), never a compass score.
Dual engine (mandatory)
| Engine | Role |
|---|---|
| Deterministic | CLI / MCP / contract sensors — exit codes, plan kinds, coverage numbers, install status |
| Exploratory | You open this repo's real files and product surface before concluding |
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.
- 3d 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 3d ago), licensed MIT. It adds 25 tokens to every session and 2,547 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
architecture-patterns
Software architecture patterns and best practices.
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…
tsq-ddd
Domain-Driven Design 전략적 설계 가이드라인. Bounded Context, Ubiquitous Language, Context Map. Use when: 도메인 모델링, Bounded Context 설계, 유비쿼터스 언어 정의, 컨텍스트 맵 작성 시.
ddd-aggregate-modeling
Guides aggregate modeling decisions for DDD services: aggregate root boundaries, child entity vs value object decisions, invariants, snapshot/primitives mapping, specification/criteria usage, and repository contract design. Invoked when the user asks to model or refactor domain entities and aggregate behavior.
AWS WAF Pillar Review
AWS Well-Architected Framework pillar checklists — operational excellence, security, reliability, performance efficiency, cost optimization, sustainability — for reviewing AWS infrastructure changes.
Azure WAF Pillar Review
Azure-specific Well-Architected Framework pillar checklists — reliability, security, cost optimization, operational excellence, performance efficiency — for reviewing Azure infrastructure changes.