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.
git clone --depth 1 https://github.com/Matt-Dionis/claude-code-configsWrote 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/commands/matt-dionis/claude-code-configs/setup-form)<a href="https://agentmods.dev/commands/matt-dionis/claude-code-configs/setup-form"><img src="https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/setup-form/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/commands/matt-dionis/claude-code-configs/setup-form"><img src="https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/setup-form.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.00012 | $0.00768 |
| Opus 5.5 | $0.00005 | $0.00307 |
| Sonnet 5.5 | $0.00002 | $0.00154 |
| Haiku 4.5 | $0.00001 | $0.00077 |
Grade A, and why
setup-form 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 1mo 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a complete form setup with React Hook Form, Zod validation, and shadcn/ui form components.
Instructions
-
Install required dependencies if not present:
react-hook-form@hookform/resolverszod- Required shadcn components:
form,input,button, etc.
-
Create the form with:
- Zod schema for validation
- Form component with React Hook Form
- Proper error handling
- Loading states
- Success feedback
Template Structure
// lib/validations/[form-name].ts
import * as z from "zod"
export const [formName]Schema = z.object({
// Define fields
})
export type [FormName]Values = z.infer<typeof [formName]Schema>
// components/forms/[form-name]-form.tsx
import { useForm } from "react-hook-form"
import { zodResolver } from "@hookform/resolvers/zod"
import { [formName]Schema, type [FormName]Values } from "@/lib/validations/[form-name]"
import {
Form,
FormControl,
FormDescription,
FormField,
FormItem,
FormLabel,
FormMessage,
} from "@/components/ui/form"
import { Input } from "@/components/ui/input"
import { Button } from "@/components/ui/button"
import { toast } from "@/components/ui/use-toast"
export function [FormName]Form() {
const form = useForm<[FormName]Values>({
resolver: zodResolver([formName]Schema),
defaultValues: {
// Set defaults
},
})
async function onSubmit(data: [FormName]Values) {
try {
// Handle submission
toast({
title: "Success",
description: "Form submitted successfully",
})
} catch (error) {
toast({
title: "Error",
description: "Something went wrong",
variant: "destructive",
})
}
}
return (
<Form {...form}>
<form onSubmit={form.handleSubmit(onSubmit)} className="space-y-6">
{/* Form fields */}
<Button
type="submit"
disabled={form.formState.isSubmitting}
>
{form.formState.isSubmitting ? "Submitting..." : "Submit"}
</Button>
</form>
</Form>
)
}
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.
- 1mo ago First seen · 126 lines · 12 tokens per session scan A 3043165a56e1
setup-form is a command published in the GitHub repository Matt-Dionis/claude-code-configs (619 stars, last pushed 1y ago), licensed MIT. It adds 12 tokens to every session and 768 once invoked, about $0.0000 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.
Other commands, from other repositories
plan-feature
Plan a feature from BRD-lite brief or clear intent into PRD (What), decisions, implementation plan, and task slices.
retro-learn
Convert delivery findings into skill, eval, workflow, and documentation improvements.
prototype-loop
Enter leveraged-prototype focus mode — focus marker plus normal watch/rebuild loop for visual-parity work and batch upstream framework gap-fixes.
review-arch
Review the current branch for code quality, TypeScript, and React/Next.js patterns. Supports whole-branch review or scoped review by path, feature, or base branch.
story-and-test
For the component(s) in scope.
a11y-audit-react
Identify accessibility violations in React components and provide actionable remediation aligned with WCAG 2.2 Level AA. This is the guided audit workflow that applies the standards defined in the a11y-automation and react-components rules.