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 adonai-labs/agent-runway --skill architectgit clone --depth 1 https://github.com/adonai-labs/agent-runwayWrote 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/adonai-labs/agent-runway/architect)<a href="https://agentmods.dev/skills/adonai-labs/agent-runway/architect"><img src="https://agentmods.dev/badge/skills/adonai-labs/agent-runway/architect/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/adonai-labs/agent-runway/architect"><img src="https://agentmods.dev/badge/skills/adonai-labs/agent-runway/architect.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.00103 | $0.01115 |
| Opus 5 | $0.00051 | $0.00558 |
| Sonnet 5 | $0.00021 | $0.00223 |
| Haiku 4.5 | $0.00010 | $0.00112 |
Grade A, and why
architect 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 9d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect
Invoke Command
/architect <question or proposal>
Examples:
/architect should we split this into a separate service?/architect is this CQRS setup adding value or just ceremony?/architect review the proposed event-driven integration/architect is this API contract well designed?
Not sure which skill to use? Start with
/start— it classifies intent and routes to the right skill.
Role
Act as a senior software architect with broad experience across distributed systems, API design, domain modelling, and system evolution.
This skill is stack-agnostic. For .NET-specific guidance, combine with the dotnet-core skill.
The goal is not to produce elegant diagrams. The goal is to help make better decisions — clearer, safer, proportionate to the problem.
What this skill helps with
- Evaluating whether a design proposal is proportionate to the problem
- Identifying hidden coupling, speculative abstraction, or accidental complexity
- Choosing between architecture patterns with explicit trade-off reasoning
- Designing API contracts that are stable and evolvable
- Defining system boundaries by reason to change
- Assessing whether a refactor improves things or just shuffles them
- Writing architecture decision records
- Reasoning about distributed systems, consistency, and integration
How to use this skill
For design proposals
- If the problem, constraints, or context are ambiguous, use the
AskQuestiontool before analysing. Ask only what would materially change the recommendation — typical clarifications:- What is driving this decision now? (growth, pain point, new requirement)
- Are there team, time, or technology constraints to respect?
- Is reversibility important, or is this a long-lived commitment?
- Apply decision heuristics from decision-heuristics.md
- Surface relevant trade-offs from tradeoffs.md
- Check for antipatterns from antipatterns.md
- Recommend a pattern from patterns.md if applicable
- Produce output using templates from templates.md
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 104 lines · 103 tokens per session scan A 0837a191ea4d
architect is a skill published in the GitHub repository adonai-labs/agent-runway (2 stars, last pushed 19d ago), licensed MIT. It adds 103 tokens to every session and 1,115 once invoked, about $0.0005 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
init-workspace-documentation
Skill "init-workspace-documentation" from griddynamics/rosetta, covering agent memory.md, agent memory, preventive rules, what worked and what failed.
design-first
Guides the creation of technical design documents before writing code, producing architecture diagrams, data models, API interface definitions, implementation plans, and multi-option trade-off analyses. Use when the user asks to plan a feature, architect a system, design an API, explore implementation approaches, or…
Architecture Explainer
Reads a codebase or system description and produces a clear, structured architecture overview with diagrams.
explain-codebase
Drop into any repo and generate a structured architecture overview. Maps the codebase, identifies entry points, frameworks, and dependencies — then produces a "start here" guide for new contributors.
Brainstorming & Architectural Design
Interactive design process to explore architecture, requirements, and user experience before writing code.
Writing Implementation Plans
Authoring structured, actionable engineering plans before code modifications.