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-contractgit 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-contract)<a href="https://agentmods.dev/skills/pedroknigge/arkgate/ark-contract"><img src="https://agentmods.dev/badge/skills/pedroknigge/arkgate/ark-contract/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-contract"><img src="https://agentmods.dev/badge/skills/pedroknigge/arkgate/ark-contract.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.01087 |
| Opus 5.5 | $0.00010 | $0.00435 |
| Sonnet 5.5 | $0.00005 | $0.00217 |
| Haiku 4.5 | $0.00003 | $0.00109 |
Grade A, and why
ark-contract 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 23d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ark-contract — Shortcut to adopt / autopilot
Not a first-class door. One-release redirect. Writing ark.config.json is
/ark-adopt at session 0 and /ark-autopilot afterward. Do that job now.
Contener · Guiar · Ordenar — this leftover name is not a star.
When / not when
| Use this leftover name when… | Prefer instead |
|---|---|
| Layers / include / ArkRules / first extra need an edit | /ark-adopt (path, first arkRun / first arkOrder) or /ark-autopilot (tighten) |
| False-green / concentrated edge | /ark-adopt — write the honest config |
| One kernel candidate | /ark-runtime |
| One order-plane candidate | /ark-order |
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 |
The CLI is a sensor, never the whole job. Claiming done without the exploratory bar for this skill is incomplete.
MCP workspace binding (mandatory)
Before any ark_* MCP tool, call ark_identity with project.expectedRoot set to the exact
workspace root. Continue only when binding.status === "matched" and authoritative === true;
retain projectIdentity.projectId, then pass both expectedRoot and expectedProjectId under
project on every later MCP call. If identity is missing, mismatched, unverified, or the root is
uncertain, do not consume MCP analysis: use the workspace-local CLI and report that MCP
restart/retargeting is required. ark://manifest never satisfies this preflight.
Subagent fan-out (optional, host-dependent)
If the host supports parallel subagents, fan out read-only scouts; otherwise fall back to sequential. Never weaken the gate.
Related onboarding
- Greenfield:
/ark-adoptorark-check --recommend/ark start. - Brownfield:
/ark-adopt— match config to reality.
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.
- 23d ago Changed · +17 lines 7944f0f6e305
- 27d ago Changed · +2 lines a0b7087306b4
- 1mo ago Changed · -11 lines 81eae8e0afb2
- 1mo ago Changed 21cc3b44fb48
- 1mo ago First seen · 78 lines · 25 tokens per session scan A 535c869a1e34
ark-contract 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 1,087 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.