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-explaingit 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-explain)<a href="https://agentmods.dev/skills/pedroknigge/arkgate/ark-explain"><img src="https://agentmods.dev/badge/skills/pedroknigge/arkgate/ark-explain/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-explain"><img src="https://agentmods.dev/badge/skills/pedroknigge/arkgate/ark-explain.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.00017 | $0.03739 |
| Opus 5.5 | $0.00007 | $0.01496 |
| Sonnet 5.5 | $0.00003 | $0.00748 |
| Haiku 4.5 | $0.00002 | $0.00374 |
Grade A, and why
ark-explain 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 27d 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ark-explain — Understand this project's architecture
Contener · Guiar · Ordenar. In plain words: contain the write, guide the next step, order leftover mess. This door is Guiar: teach the path in plain language. Skills never enforce — CLI / hooks / CI do.
Not a first-run door. Teach / HTML tour only. Session 0 → /ark-adopt.
Map → /ark-explore. Apply → /ark-autopilot.
Wire ArkRun → /ark-runtime. Wire ArkOrder → /ark-order.
The user wants to understand the architecture, a specific rule, or why the gate blocked them.
Improvement compass (process preflight)
When doctor is available, read doctor.improvementCompass (or the human Improvement compass section).
Name 1–3 residual lenses in plain language before skill-shopping. Always notAScore — never invent
0–10 scores or Excellent/Good ranks.
What the user should feel next: fewer blocked AI writes, clearer folders, safer domain — then jargon.
Anti false-done: empty plan A + residual lenses / design-weak → Incomplete? yes. Green edges alone are not “architecture finished.” A doctor green / Healthy line must name a file, config key, or test; uncited green is unfinished.
AI-easy architecture: ports over concrete I/O in domain; one concern per module; golden pattern for
new files; place before write (/ark-place / prepare-write).
Out of scope (honest): scalability/performance, full app-security tooling (SAST), and full resilience patterns are out-of-scope lenses — say so; do not invent Ark enforcement for them.
Tour by lenses (teach, not score). Prefer showcase HTML + doctor compass section when explaining residual.
When / not when
Use /ark-explain when… |
Do not use it when… |
|---|---|
| Plain-language tour of layers/rules/report | Decision-grade recon / dual-plan → /ark-explore |
| “Why did the gate block me?” pedagogy | Apply fixes → /ark-autopilot |
| Generate / walk HTML showcase report | Fitness numbers only → /ark-coverage; brownfield action → /ark-adopt |
| Your job is to teach with this repo's real data and leave a shareable visual artifact. |
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.
- 27d ago Changed · +2 lines 843da2335954
- 28d ago Changed ba8794464ed8
- 1mo ago Changed · +3 lines bc7c8dc71892
- 1mo ago Changed · +1 lines 1537d3f49ddc
- 1mo ago Changed · +1 lines ce6e6914fdce
- 1mo ago Changed · +1 lines dde325c0fcea
- 1mo ago Changed · +4 lines b9803acd5a01
- 1mo ago Changed · +1 lines 9bfd28cfde0e
- 1mo ago First seen · 241 lines · 17 tokens per session scan A d65a7050aefe
ark-explain is a skill published in the GitHub repository pedroknigge/arkgate (1 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 3,739 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.