create-modus-form-component

create-modus-form-component is a skill for Cursor from julianoczkowski/create-trimble-app. It costs 26 tokens per session (3,100 once invoked), scanned A, original, MIT.

A pattern for building forms with Modus input components, including text fields, checkboxes, buttons, validation messages, and accessible labels.

In plain words
What is it for?
Use it to create registration, contact, multi-step, or other React forms with Modus controls and validation.
Why use it?
It provides a consistent way to read input values, show validation feedback, and submit forms while accounting for a known checkbox-value problem.

Skill for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it to create registration, contact, multi-step, or other React forms with Modus controls and validation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/julianoczkowski/create-trimble-app/create-modus-form-component
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.

Any agent
npx skills add julianoczkowski/create-trimble-app --skill create-modus-form-component
Clone the repo
git clone --depth 1 https://github.com/julianoczkowski/create-trimble-app

Made for: Cursor.

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 create-modus-form-component

README.md
[![agentmods](https://agentmods.dev/badge/skills/julianoczkowski/create-trimble-app/create-modus-form-component/github.svg)](https://agentmods.dev/skills/julianoczkowski/create-trimble-app/create-modus-form-component)
Your own site
<a href="https://agentmods.dev/skills/julianoczkowski/create-trimble-app/create-modus-form-component"><img src="https://agentmods.dev/badge/skills/julianoczkowski/create-trimble-app/create-modus-form-component/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 create-modus-form-component

Your own site · 80×15
<a href="https://agentmods.dev/skills/julianoczkowski/create-trimble-app/create-modus-form-component"><img src="https://agentmods.dev/badge/skills/julianoczkowski/create-trimble-app/create-modus-form-component.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,100 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.00026 $0.03100
Opus 5.5 $0.00010 $0.01240
Sonnet 5.5 $0.00005 $0.00620
Haiku 4.5 $0.00003 $0.00310

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

Security

Grade A, and why

create-modus-form-component 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.

templates/react/.cursor/skills/create-modus-form-component/SKILL.md · 519 lines

How it starts

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

Create Modus Form Component

Scaffold form components with proper Modus input integration, event handling, validation feedback, and checkbox bug handling.

When to Use

Use this skill when:

  • Creating forms with Modus input components
  • Building multi-step forms
  • Implementing form validation
  • Handling form submissions
  • Creating user registration or contact forms

Pattern Overview

Modus forms follow these patterns:

  1. Use Modus input components (ModusTextInput, ModusCheckbox, etc.)
  2. Handle input changes with proper event handlers
  3. Apply checkbox value inversion automatically
  4. Use ModusInputFeedback for validation messages
  5. Include proper accessibility attributes
  6. Handle form submission with ModusButton

Basic Form Template

"use client";

import { useState } from "react";
import ModusTextInput from "./components/ModusTextInput";
import ModusCheckbox from "./components/ModusCheckbox";
import ModusButton from "./components/ModusButton";
import ModusInputFeedback from "./components/ModusInputFeedback";
import ModusInputLabel from "./components/ModusInputLabel";

interface FormData {
  name: string;
  email: string;
  agreeToTerms: boolean;
}

export default function ContactForm() {
  const [formData, setFormData] = useState<FormData>({
    name: "",
    email: "",
    agreeToTerms: false,
  });

  const [errors, setErrors] = useState<Partial<Record<keyof FormData, string>>>({});

  const updateField = (field: keyof FormData, value: string | boolean) => {
    setFormData(prev => ({ ...prev, [field]: value }));
    // Clear error when user starts typing
    if (errors[field]) {
      setErrors(prev => ({ ...prev, [field]: undefined }));
    }
  };

  const validateForm = (): boolean => {
    const newErrors: Partial<Record<keyof FormData, string>> = {};

    if (!formData.name.trim()) {
      newErrors.name = "Name is required";
    }

    if (!formData.email.trim()) {
      newErrors.email = "Email is required";
    } else if (!/^[^\s@]+@[^\s@]+\.[^\s@]+$/.test(formData.email)) {
      newErrors.email = "Please enter a valid email address";
    }

    if (!formData.agreeToTerms) {
      newErrors.agreeToTerms = "You must agree to the terms";
    }

    setErrors(newErrors);
    return Object.keys(newErrors).length === 0;
  };

  const handleSubmit = () => {
    if (validateForm()) {
      console.log("Form submitted:", formData);
      // Handle form submission
    }
  };

  return (
    <div className="max-w-md mx-auto p-6 bg-card border-default rounded-lg">
      <div className="text-2xl font-bold mb-6 text-foreground">
        Contact Us
      </div>

      <div className="space-y-4">
        {/* Name Field */}
        <div>
          <ModusInputLabel
            label="Name"
            required
            size="md"
          />
          <ModusTextInput
            value={formData.name}
            onInputChange={(event) => {
              const value = (event.target as HTMLModusWcTextInputElement).value;
              updateField("name", value);
            }}
            placeholder="Enter your name"
            required
            size="md"
          />
          {errors.name && (
            <ModusInputFeedback
              message={errors.name}
              type="error"
              size="md"
            />
          )}
        </div>

        {/* Email Field */}
        <div>
          <ModusInputLabel
            label="Email"
            required
            size="md"
          />
          <ModusTextInput
            type="email"
            value={formData.email}
            onInputChange={(event) => {
              const value = (event.target as HTMLModusWcTextInputElement).value;
              updateField("email", value);
            }}
            placeholder="Enter your email"
            required
            size="md"
          />
          {errors.email && (
            <ModusInputFeedback
              message={errors.email}
              type="error"
              size="md"
            />
          )}
        </div>

        {/* Checkbox Field */}
        <div>
          <ModusCheckbox
            label="I agree to the terms and conditions"
            value={formData.agreeToTerms}
            onValueChange={(event) => {
              // ✅ Checkbox value is already corrected (inverted) by wrapper
              updateField("agreeToTerms", event.detail);
            }}
            required
            size="md"
          />
          {errors.agreeToTerms && (
            <ModusInputFeedback
              message={errors.agreeToTerms}
              type="error"
              size="md"
            />
          )}
        </div>

        {/* Submit Button */}
        <div className="flex gap-2 pt-4">
          <ModusButton
            color="primary"
            variant="filled"
            onButtonClick={handleSubmit}
          >
            Submit
          </ModusButton>
          <ModusButton
            variant="borderless"
            onButtonClick={() => {
              setFormData({ name: "", email: "", agreeToTerms: false });
              setErrors({});
            }}
          >
            Reset
          </ModusButton>
        </div>
      </div>
    </div>
  );
}

Read the full file on GitHub · 519 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.

  1. 2mo ago First seen · 519 lines · 26 tokens per session scan A 7bd50bd42343

Subscribe to this mod's changes

create-modus-form-component is a skill published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 4mo ago), licensed MIT. It adds 26 tokens to every session and 3,100 once invoked, about $0.0001 per session on Opus 5.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.

Related

create-modus-form-component compared with skills from other repositories

create-modus-form-component next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
create-modus-form-componentjulianoczkowski/create-trimble-appSkill34mo agoMITA26Cursor
test-failure-explorerQwenLM/qwen-codeSkill29kyesterdayApache-2.0A32Claude Code, Codex
confirm-failures-are-causally-linked-to-the-task-before-reportinZaxbyHub/opencode-swarmSkill518todayMITA29OpenCode
include-test-files-that-assert-on-behavior-being-changed-in-declZaxbyHub/opencode-swarmSkill518todayMITA29OpenCode
run-failing-tests-immediately-after-test-gate-failureZaxbyHub/opencode-swarmSkill518todayMITA21OpenCode
run-test-suite-after-registration-changesZaxbyHub/opencode-swarmSkill518todayMITA14OpenCode
caliber-testingcaliber-ai-org/ai-setupSkill1.3k1mo agoMITA0Claude Code, Codex