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-thinknpx skills add pedroknigge/arkgate --skill ark-thinkgit 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-think)<a href="https://agentmods.dev/skills/pedroknigge/arkgate/ark-think"><img src="https://agentmods.dev/badge/skills/pedroknigge/arkgate/ark-think.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.00028 | $0.02762 |
| Opus 5 | $0.00014 | $0.01381 |
| Sonnet 5 | $0.00006 | $0.00552 |
| Haiku 4.5 | $0.00003 | $0.00276 |
Grade A, and why
ark-think 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 yesterday.
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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ark-think — Architectural reasoning (host LLM only)
Not a first-run door. One decision only. Session 0 → /ark-adopt.
Full map → /ark-explore. Apply → /ark-autopilot.
Do not send the user to leftover /ark-contract or /ark-fix.
You are the user's architecture thinking partner inside the project's Ark contract. This skill does not call any LLM API from the arkgate package. You (the host agent) reason; the write-gate and CI remain deterministic.
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.”
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.
2–3 options labeled by lens impact (what residual improves / what stays out-of-scope).
Deep modules (process)
- Prefer deep modules (small interface, hidden complexity). Never invent a depth score.
- Label the seam on each option that introduces a port/adapter; apply the deletion test before pass-through extracts “for testability.”
- Recommend tests at the public interface of the chosen seam.
When / not when
Use /ark-think when… |
Do not use it when… |
|---|---|
| One decision: new layer vs slice, port vs shared, peerIsolation choice | Full map / ranked residual / dual-plan seed → /ark-explore |
| 2–3 options already bounded by a known surface | Apply remediation → /ark-autopilot |
| Trade-offs before writing a new feature | Brownfield config wrong / false-green → /ark-adopt |
| Explain why a rule exists in this tree | HTML tour → /ark-explain; fitness numbers → /ark-coverage |
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.
- yesterday Changed c855495faf3e
- 5d ago First seen · 171 lines · 28 tokens per session scan A 267d44f2f058
ark-think is a skill published in the GitHub repository pedroknigge/arkgate (1 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 2,762 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…