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 expressgit 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/express)<a href="https://agentmods.dev/skills/adonai-labs/agent-runway/express"><img src="https://agentmods.dev/badge/skills/adonai-labs/agent-runway/express/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/express"><img src="https://agentmods.dev/badge/skills/adonai-labs/agent-runway/express.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.00063 | $0.01410 |
| Opus 5 | $0.00032 | $0.00705 |
| Sonnet 5 | $0.00013 | $0.00282 |
| Haiku 4.5 | $0.00006 | $0.00141 |
Grade A, and why
express 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Express
Invoke Command
/express <description of what you want to build or fix>
Examples:
/express add null guard to OrderService.GetById/express fix missing ConfigureAwait on async database call in PaymentHandler/express add X-Correlation-Id header to outbound HTTP requests
Not sure if
/expressis right for this task? Run/startfirst — it will tell you whether the task fits/expressor needs more ceremony.
What this skill does
Five phases. No approval gates except one: escalation signal confirmation if signals are detected in Phase 0.
The developer owns all design decisions. This skill enforces critical safety checks and a lightweight self-review — nothing more.
/express is not /lead Fast-Track Mode with fewer phases. It is a different skill designed from the ground up for minimal friction. It assumes the developer has full context, knows the codebase, and does not need a planning step.
Escalation signals
Checked in Phase 0. Also surface inline during Phase 2 if unexpected complexity emerges.
Signals are non-blocking — the developer always sees them and always decides. They are never a hard stop.
Simplicity policy:
/expressis only for low-risk, reversible, low-uncertainty changes.- If risk profile does not match this, recommend
/leadand stop instead of stretching/express.
Detection criteria
| Signal | Condition |
|---|---|
| Contract change | The change modifies a public API, shared interface, or data contract consumed by other components or services |
| Cross-boundary | The change touches more than one bounded context, service, or application layer in a non-trivial way |
| Security surface | The change involves authentication, authorisation, input validation, secrets, or data exposure |
| Data migration | The change requires a schema change or data transformation that cannot be easily rolled back |
| Multi-service coordination | The change requires coordinated deployment or configuration across more than one service |
| Unknown territory | The developer's description suggests unfamiliarity with the part of the codebase being changed |
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 · 145 lines · 63 tokens per session scan A 0219899a71e0
express is a skill published in the GitHub repository adonai-labs/agent-runway (2 stars, last pushed 19d ago), licensed MIT. It adds 63 tokens to every session and 1,410 once invoked, about $0.0003 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
sdd-apply
Skill "sdd-apply" from Gentleman-Programming/gentle-ai, covering execution role, language domain contract, purpose, what you receive and execution and persistence contract.
next-action
Use when the user wants a next-action recommendation based on current state — reads handoff/git/lessons/STATE and proposes top-3 by impact. Trigger: '/next', 'what should I do next', 'next action'. Proposes only, never executes.
kafka-dlq-review
Review dead letter queue implementations for completeness using the Lenses MCP server. Checks DLQ topic existence, configuration, monitoring, metadata preservation, retry logic, reprocessing paths and connector DLQ alignment. Use when user says "review dead letter queues", "check DLQ setup", "DLQ audit" or asks about…
kafka-connector-review
Review Kafka Connect connector configurations for common misconfigurations using the Lenses MCP server. Checks error handling, DLQ setup, converters, transforms, task count and task health. Use when user says "review connectors", "check connector configs", "why is my connector failing" or asks about Kafka Connect…
kafka-perf-review
Review Kafka producer and consumer performance configurations in both the live cluster (via Lenses MCP) and the codebase. Flags un-tuned defaults, anti-patterns and missing best practices. Use when user says "review Kafka performance", "check producer configs", "tune Kafka settings" or asks about throughput, batching…
kafka-schema-review
Review Kafka schema changes (Avro, Protobuf, JSON Schema) for compatibility and evolution best practices using the Lenses MCP server. Detects breaking changes, missing defaults, schema drift and naming issues. Use when user says "review schema changes", "check schema compatibility", "will this schema break consumers"…