agentmods.dev

tidyfactor-design: Command for Claude Code

.agents/skills/tidyfactor-design/references/commands/deploy.md

deploy is a command for Claude Code from alwkala/tidyfactor-design. It costs 0 tokens per session (469 once invoked), scanned A, original, MIT.

A final command for checking a clickable prototype and preparing it for presentation or developer handoff without a build step.

In plain words
What is it for?
Use it to run the prototype locally, check its presentation toolbar, confirm that the pages work through ordinary static file serving, and prepare an optional handoff note.
Why use it?
It catches problems in navigation, page states, and static hosting before the prototype is shared.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md). Also seen: installed under .agents/ (shared by several agents).

This is alwkala/tidyfactor-design's own configuration. It tells Claude Code how to work on tidyfactor-design itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything tidyfactor-design configures →

not rated 6repo 3mo ago A scan 0 tokens original MIT
View source ↗ alwkala/tidyfactor-design alwkala.com
Reuse

Borrowing it

Nothing to install: this file belongs to alwkala/tidyfactor-design. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/alwkala/tidyfactor-design/main/.agents/skills/tidyfactor-design/references/commands/deploy.md
Clone the repo
git clone --depth 1 https://github.com/alwkala/tidyfactor-design

Made for: Claude Code.

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.

agentmods badge for deploy

README.md
[![agentmods](https://agentmods.dev/badge/commands/alwkala/tidyfactor-design/deploy/github.svg)](https://agentmods.dev/commands/alwkala/tidyfactor-design/deploy)
Your own site
<a href="https://agentmods.dev/commands/alwkala/tidyfactor-design/deploy"><img src="https://agentmods.dev/badge/commands/alwkala/tidyfactor-design/deploy/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.

agentmods 80×15 button for deploy

Your own site · 80×15
<a href="https://agentmods.dev/commands/alwkala/tidyfactor-design/deploy"><img src="https://agentmods.dev/badge/commands/alwkala/tidyfactor-design/deploy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 469 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00469
Opus 5.5 $0.00000 $0.00188
Sonnet 5.5 $0.00000 $0.00094
Haiku 4.5 $0.00000 $0.00047

Measured 2mo ago against content hash 189d578bd219, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

deploy 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 2mo 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.

.agents/skills/tidyfactor-design/references/commands/deploy.md · 46 lines

What it actually says

Command: deploy — Preview, Present, Export

Purpose

Always the last command: verify the prototype actually behaves correctly and package it for a client presentation or a developer handoff, with zero build step required either way.

When to run it

  • Always last in a full sequence, after audit passes.
  • User phrasing: "get this ready to present", "export the prototype", deploy.

What it does

  1. Serve locally: python -m http.server 8123 or npx serve — open in a visible browser tab (backgrounded tabs pause requestAnimationFrame, which affects motion's entrance/scroll effects and can produce false verification results).
  2. Present mode: confirm proto-nav.js's toolbar works — page jump, flow start, state toggles — this is the client-facing "click through it yourself" experience.
  3. Confirm portability: the whole pages/ + design-system/ folder runs correctly opened via plain static file serving — no server process, no build step, matches the zero-dependency promise of every TidyFactor track's output, whatever the CSS foundation needed at design time.
  4. Handoff note (optional, never assumed): if the user wants this handed to tidyfactor-html/tidyfactor-php-* for production, that's a separate, explicit request — deploy doesn't restructure anything toward another skill's conventions unasked.
  5. Final audit pass — nothing ships to a client review with open structural violations.

Output convention

project/
  design-system/   ← shipped as-is, still the only source of styling
  pages/
  proto-nav.js       (strip before any production handoff — it's a dev tool)

Checklist

  • Verified in a visible browser tab
  • proto-nav.js present-mode toolbar functions correctly
  • Runs from plain static file serving, no build step
  • Final audit clean (or open findings explicitly accepted by the user)
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.

  1. 2mo ago First seen · 46 lines · 0 tokens per session scan A 189d578bd219

Subscribe to this mod's changes

deploy is a command published in the GitHub repository alwkala/tidyfactor-design (6 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 469 tokens. 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.

Testingai-agentai-agentsai-codingai-toolscoding-agentdesign-system
Related

deploy compared with commands from other repositories

deploy next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
deployalwkala/tidyfactor-designCommand63mo agoMITA0Claude Code
agentloop-audit-queryalibaba/loongsuite-pilotCommand239yesterdayApache-2.0A5Claude Code
critique-screenOwl-Listener/designer-skillsCommand3.3k2mo agoMITA16Claude Code
critique-uxOwl-Listener/designer-skillsCommand3.3k2mo agoMITA26Claude Code
pull-repostravisjneuman/.claudeCommand107yesterdayMITA13Claude Code
design-onboardingOwl-Listener/designer-skillsCommand3.3k2mo agoMITA21Claude Code
frame-problemOwl-Listener/designer-skillsCommand3.3k2mo agoMITA15Claude Code