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-placegit 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-place)<a href="https://agentmods.dev/skills/pedroknigge/arkgate/ark-place"><img src="https://agentmods.dev/badge/skills/pedroknigge/arkgate/ark-place.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.1 | $0.00022 | $0.04931 |
| Opus 5 | $0.00011 | $0.02465 |
| Sonnet 5 | $0.00004 | $0.00986 |
| Haiku 4.5 | $0.00002 | $0.00493 |
Grade A, and why
ark-place 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 today.
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 — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ark-place — Where does this code go?
Contener · Guiar · Ordenar. In plain words: contain the write, guide the next step, order leftover mess. This door is Contener: write the new file in the right house. Skills never enforce — CLI / hooks / CI do.
When: you are adding a new file or artifact and need the layer, folder, and name.
Not when: session 0 / config is missing or lying (/ark-adopt) or an existing violation cluster (/ark-autopilot).
Steps
- CLI-first: if the local CLI already resolved the root, skip waiting on MCP. Identity is optional then.
- Place with filePath required (
ark_placeor readark.config.json+.ark/golden-pattern.json). Fail-closed without a path — never inventcomponents/*.tsxor default to Presentation. - Write it there. Then
arkgate-check.
Checklist
filePathis known before the call. Description alone is not a path.- Golden pattern is load-bearing when present. Adopt generates it.
- An included file that matches no layer is not a pass. The write gate denies it
(
CONFIG_UNCLASSIFIED_FILES). Place it in a layer folder, or send include/layer drift to/ark-adopt. Do not write into a loose include gap. - Do not default a repository to Presentation.
- When the matched layer has
layers[].description, print that caption next to the layer name and globs. Omit when absent — do not invent a caption or/ark-describe. - When
arkRunis on: scaffold through the kernel (nonewof managed types; declareuses/reactsTo/raises/sends; factory only inarkRun.kernelRoots,compositionRootsalias). Extra off → do not introduce the kernel. Enable it via/ark-adopt. Skills never enforce. - When
arkOrderis on: factory only inarkOrder.planeRoots; Domain stays plane-free; first freeze ξ withrelease(); later ξ isproposeReleasethenapply. Extra off → do not introduce the plane. Enable it via/ark-adopt. Skills never enforce.
Autonomy contract
Invoking this skill is the approval. If the user described an artifact, write the
files in this turn (prepare-write + scaffold). A path table alone is incomplete.
The CLI is a sensor and gate. CLI budget: ark_identity then ark_place when using MCP
(or skip identity if the CLI already resolved the root); otherwise read ark.config.json; write;
ark-check. Do not ask which layer they prefer.
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.
- today Changed · +3 lines 82d5bd055d0d
- yesterday Changed · +270 lines · +1 tokens per session 798df0e344fe
- 7d ago First seen · 11 lines · 21 tokens per session scan A 210be9f1e567
ark-place is a skill published in the GitHub repository pedroknigge/arkgate (1 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 4,931 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.
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…