What is adaptive-crusade?

An adaptive-interface audit command that checks how a user interface behaves across foldable devices, multiple monitors, tablets, split-screen layouts, touch input, keyboards, and high-resolution screens.

Use it to inspect all or selected backend or frontend areas for viewport assumptions, touch-target problems, focus handling, DPI issues, and state loss.

It helps uncover layout, accessibility, image-quality, and state-preservation problems that may appear when the screen size, orientation, input method, or display density changes. It can report issues and apply automatic fixes where possible.

adaptive-crusade — Command for Claude Code by btachinardi

Install

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.

Clone the repo

git clone --depth 1 https://github.com/btachinardi/church

Made for: Claude Code.

Or install church, the plugin that ships this one along with the rest of its 1 skill, 14 commands, 14 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/btachinardi/church/adaptive-crusade/github.svg)](https://agentmods.dev/commands/btachinardi/church/adaptive-crusade)

Your own site

<a href="https://agentmods.dev/commands/btachinardi/church/adaptive-crusade"><img src="https://agentmods.dev/badge/commands/btachinardi/church/adaptive-crusade/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/btachinardi/church/adaptive-crusade"><img src="https://agentmods.dev/badge/commands/btachinardi/church/adaptive-crusade.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,844 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00039	$0.02844
Opus 5	$0.00019	$0.01422
Sonnet 5	$0.00008	$0.00569
Haiku 4.5	$0.00004	$0.00284

Measured 10d ago against content hash 0c31a39af954, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

adaptive-crusade 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 10d 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.

commands/adaptive-crusade.md · 348 lines

How it starts

The opening of the file, as written. The whole thing — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the Adaptive Crusade Orchestrator, commanding squads of Adaptive UI Purist agents in a coordinated assault on every viewport sin lurking in the codebase.

THE MISSION

The Great Viewport Collapse approaches. Foldable devices fold. Multi-monitor setups span. Tablets rotate. Split-screen mode halves. Touch fingers tap. Keyboard users tab. High-DPI displays demand crisp pixels. And somewhere in this codebase, a 100vw waits to SHATTER, an outline: none waits to BLIND, a 24px button waits to FRUSTRATE, and an <img> without srcset waits to SMEAR.

Your mission: Find every adaptive UI violation. Audit every viewport assumption. Enforce the Nine Commandments of Adaptive UI.

This is not a responsive design check. This is a CRUSADE.

PHASE 1: RECONNAISSANCE

Before deploying specialist squads, you must MAP THE BATTLEFIELD.

Step 1: Parse Arguments

Extract from the user's command:

Path: Which directory to scan (default: current working directory)
--fix: Apply automatic fixes where possible (default: report-only mode)
--scope: Filter to specific areas
- all (default): Scan everything
- api: Only backend files (apps/api, packages if relevant)
- web: Only frontend files (apps/web, packages/ui)
- Custom path: User provides specific directory
--concern: Filter to specific squads
- seam: Only viewport segments and hinge awareness
- state: Only state preservation
- focus: Only focus management
- dpi: Only resolution and DPI
- touch: Only touch targets and hover
- Not specified: All concerns (default)

Step 2: Scan the Codebase

CRITICAL: ALWAYS exclude node_modules/, dist/, build/, .next/, coverage/ from searches. Use the Glob tool which respects .gitignore automatically, or add explicit exclusions to bash commands.

Scan for these violation categories:

Seam Violations:

Grep for 100vw and 100vh in CSS, SCSS, and TSX files
Grep for env(viewport-segment to check adoption
Check for viewport meta tag
Look for fixed-width containers

Read the full file on GitHub · 348 lines

Changes

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.

10d ago First seen · 348 lines · 0 tokens per session scan A 0c31a39af954

Subscribe to this mod's changes

adaptive-crusade is a command published in the GitHub repository btachinardi/church (58 stars, last pushed 5mo ago), licensed MIT. It adds 39 tokens to every session and 2,844 once invoked, about $0.0002 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-30.

Design and UX Frontend

seed-create-component

A command for creating a new SEED Design component, including its source specification, recipes, React implementation, documentation, examples, and optional headless layer.

daangn/seed-design · 12 tokens

sddesign

Full spec-driven pipeline — walks brief → tokens → shape (spec) → craft (build) → converge → ship in one guided run. Writes .ui-craft/spec.md. Run when starting a net-new surface from scratch.

educlopez/ui-craft · 46 tokens

craft

One-shot build pipeline for a complete surface from an outcome recipe — inputs (or defaults) → composition → theme → build order → acceptance bar. Use when the user asks for a whole surface ("build me a dashboard", "I need a landing page") and expects a shippable result, not component-level help.

educlopez/ui-craft · 64 tokens

adaptive-crusade