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-explorenpx skills add pedroknigge/arkgate --skill ark-exploregit 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-explore)<a href="https://agentmods.dev/skills/pedroknigge/arkgate/ark-explore"><img src="https://agentmods.dev/badge/skills/pedroknigge/arkgate/ark-explore.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.00024 | $0.08169 |
| Opus 5 | $0.00012 | $0.04084 |
| Sonnet 5 | $0.00005 | $0.01634 |
| Haiku 4.5 | $0.00002 | $0.00817 |
Grade A, and why
ark-explore 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 — 472 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ark-explore — Recon the real project (map only)
When: you need a map, or leftover design work remains after imports look green.
Not when: the user wants edits applied (/ark-autopilot) or session 0 (/ark-adopt).
Steps
- Read
arkgate-check --doctor. - Open the real tree (≥12 files across ≥4 dirs). CLI JSON alone is incomplete.
- Rank leftover work. Hand off to
/ark-autopilotto apply one refactor. Do not write config or product code here.
Checklist
- Doctor #1: if ENFORCE + empty plan A and gates are already installed → Shape (
/ark-explorethen/ark-autopilot). Do not say install-agent-gates. - Distinguish missing skills vs stale catalog. Installed ≠ stale.
- Hook green is not tree green (scripted edits bypass PreToolUse).
- Bug / false green / false red / missing doc / improvable behavior in ArkGate itself → draft one upstream GitHub issue (
pedroknigge/arkgateor the installed packagerepository.url), ask the human to confirm send, thengh issue create. Never auto-file. Never file ArkGate defects on the consumer product repo.
Autonomy contract
Invoking this skill is the approval to map. Open the real tree. CLI JSON alone is
incomplete. Do not write config or product code (that is /ark-adopt / /ark-autopilot).
CLI budget: one doctor / coverage; then open ≥12 files across ≥4 dirs; then the map.
Still never: weaken the config; invent mechanical-safe kinds; claim healthy because
plan A is empty while leftover design work remains; auto-file GitHub issues; file ArkGate
defects on the consumer product repo; skip the human confirm step.
Report ArkGate defects (ask first)
This skill maps this tree. If recon shows a bug, false green, false red, missing doc, or
improvable behavior in ArkGate itself (the arkgate package — not leftover design in the
consumer app):
- Draft one GitHub issue for upstream (
pedroknigge/arkgate, orpackage.jsonrepository.urlof the installedarkgatepackage). - Ask the human in the loop to confirm send. Do not create the issue until they say yes.
- If confirmed,
gh issue createwith the logged-in account. One finding per issue. Include repro commands, version, and measured evidence. - Never auto-file, batch-spam, or skip confirm. Never file ArkGate defects on the consumer product repo.
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 · +22 lines 73d154728dc7
- 4d ago First seen · 450 lines · 24 tokens per session scan A dca1774c4a36
ark-explore is a skill published in the GitHub repository pedroknigge/arkgate (1 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 8,169 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-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.
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.