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/arbazkhan971/godmode/formsnpx skills add arbazkhan971/godmode --skill formsgit clone --depth 1 https://github.com/arbazkhan971/godmodeWrote 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/arbazkhan971/godmode/forms)<a href="https://agentmods.dev/skills/arbazkhan971/godmode/forms"><img src="https://agentmods.dev/badge/skills/arbazkhan971/godmode/forms.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.00056 | $0.01652 |
| Opus 5 | $0.00028 | $0.00826 |
| Sonnet 5 | $0.00011 | $0.00330 |
| Haiku 4.5 | $0.00006 | $0.00165 |
Grade A, and why
forms 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 today.
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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forms — Form Architecture
Activate When
- User invokes
/godmode:forms - User says "form validation", "multi-step form", "wizard"
- When building any form beyond a simple single input
- When handling file uploads or auditing form a11y
Workflow
Step 1: Assess Form Requirements
# Detect form libraries
grep -l "react-hook-form\|formik\|@hookform" \
package.json 2>/dev/null
# Detect validation libraries
grep -l "zod\|yup\|joi\|superstruct" \
package.json 2>/dev/null
# Count existing form components
find src/ -name "*form*" -o -name "*Form*" \
2>/dev/null | wc -l
FORM REQUIREMENTS:
Purpose: <registration/checkout/settings/survey>
Framework: <React/Vue/Angular/Svelte>
Fields: <N> total
Multi-step: YES/NO (<N> steps)
File uploads: YES/NO (<types, max size>)
Async validation: YES/NO (uniqueness checks)
IF fields > 5: use React Hook Form (not useState)
IF multi-step: persist state in sessionStorage
IF file uploads: validate MIME, size, count client-side
Step 2: Form State Management
DECISION MATRIX:
| Criterion | RHF | Formik | Native |
|--------------|--------|--------|--------|
| Re-renders | Min | Freq | Min |
| Bundle size | ~9KB | ~15KB | 0KB |
| TypeScript | Excl. | Good | Manual |
| Complex forms| Excl. | Good | Verbose|
IF fields <= 3 AND no validation: native useState OK
IF fields > 3 OR has validation: React Hook Form
IF existing Formik codebase: keep Formik
Step 3: Validation Patterns
VALIDATION TIMING:
On blur (first visit): show after user leaves field
On change (after error): re-validate immediately
On submit: validate all, focus first error
Never on mount: no errors before interaction
CLIENT + SERVER SHARED SCHEMA (Zod):
Single schema shared between client and server
Client: fast UX feedback
Server: security (never trust client)
ASYNC VALIDATION:
Debounce: 500ms minimum
Show loading indicator during check
Cancel previous request on new input
THRESHOLDS:
Debounce delay: 300-500ms for async validation
Max file size: 10MB default (configurable)
Max file count: 10 per upload field
Form submission timeout: 30 seconds
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.
- today First seen · 230 lines · 56 tokens per session scan A 80067649d94f
forms is a skill published in the GitHub repository arbazkhan971/godmode (26 stars, last pushed 6d ago), licensed MIT. It adds 56 tokens to every session and 1,652 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-09-03.
Other skills, from other repositories
jobs-to-be-done
Discover what customers truly need by analyzing the "job" they hire your product to do. Use when the user mentions "customer discovery", "why customers churn", "what job does this solve", "competing against luck", "product-market fit", "switching behavior", "milkshake moment", or "functional vs emotional jobs". Also…
asc-subscription-localization
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.
scienceworld-growth-focuser
Use when you have planted a seed or need to track a plant's growth stage (sprouting, flowering, reproduction). Applies the 'focus on' action to a specific plant or biological entity to signal intent and monitor its development. Trigger after planting or when you need to observe life cycle progression in the…
ralph-specum-requirements
This skill should be used only when the user explicitly asks to use $ralph-specum-requirements, or explicitly asks Ralph Specum in Codex to run the requirements phase.
biome
Repository guidance for using Biome as the formatter, linter, and code quality tool within the hr-skills monorepo.
dashboard-builder
Build and manage recurring dashboard views of key metrics — set up daily/weekly monitoring with saved metrics and segments. Use when the user wants to create a recurring dashboard, set up KPI monitoring, or establish a baseline.