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 skills add bishopZ/2026-Boilerplate --skill add-form-managergit clone --depth 1 https://github.com/bishopZ/2026-BoilerplateWrote 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/bishopz/2026-boilerplate/add-form-manager)<a href="https://agentmods.dev/skills/bishopz/2026-boilerplate/add-form-manager"><img src="https://agentmods.dev/badge/skills/bishopz/2026-boilerplate/add-form-manager/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/skills/bishopz/2026-boilerplate/add-form-manager"><img src="https://agentmods.dev/badge/skills/bishopz/2026-boilerplate/add-form-manager.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.00022 | $0.00483 |
| Opus 5 | $0.00011 | $0.00242 |
| Sonnet 5 | $0.00004 | $0.00097 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
add-form-manager 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 12d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Form Manager (React Hook Form + Zod)
Use this skill when adding or migrating forms to a standardized form-management layer.
Goal
Adopt React Hook Form + Zod so form validation is declarative, typed, reusable, and easier to test.
Scope Guidance
- Current baseline form in this repo:
src/client/pages/Login.tsx. - Start by migrating one form end-to-end before expanding to additional forms.
- Keep UX and route behavior unchanged during migration.
Files To Update
1) Dependencies (package.json)
- Add:
react-hook-formzod@hookform/resolvers
2) Form schema and types
- Create colocated schema module (example:
src/client/pages/login-schema.ts) or sharedsrc/client/utilities/validation/. - Define a
z.object()schema and infer TS type from it. - Keep field names aligned with backend expectations (
username,password, etc.).
3) UI integration
- Replace uncontrolled form handling with
useForm. - Use
zodResolverfor validation. - Surface field-level error messages with accessible Chakra UI patterns.
- Keep submit action compatible with existing auth flow unless migration explicitly changes transport.
4) Reusable form primitives (recommended)
- If multiple forms are expected, extract reusable wrappers:
- input + label + error
- submit state handling
- validation message formatting
5) Documentation and changelog
- Update docs/README sections that describe form patterns.
- Add an
Unreleasedentry inCHANGELOG.md.
Validation Checklist
- Run
npm run lint - Run
npm run type-check - Run auth-focused E2E tests after login form migration:
npm run test:e2e -- --spec playwright/e2e/auth/login.spec.ts
- Verify keyboard navigation and error messaging remain accessible
Done Criteria
- React Hook Form + Zod are integrated and typed.
- Login form (or targeted form) is migrated without behavior regression.
- Validation and error rendering are centralized and maintainable.
- Docs/changelog are updated to reflect the new form pattern.
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.
- 12d ago First seen · 68 lines · 22 tokens per session scan A 562957910745
add-form-manager is a skill published in the GitHub repository bishopZ/2026-Boilerplate (24 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 483 once invoked, about $0.0001 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.
Other skills, from other repositories
compiler-orchestrator
Orchestrate the Rust compiler port end-to-end. Discovers the current frontier, fixes failing passes, ports new passes, reviews, and commits in a loop.
plan-update
Use when you need to update a plan document with deep research across all compiler passes. Launches parallel subagents to analyze how a topic affects every compiler phase, then consolidates findings into the plan doc.
compiler-commit
Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.
compiler-port
Port a compiler pass from TypeScript to Rust. Gathers context, plans the port, implements in a subagent with test-fix loop, then reviews.
compiler-verify
Use when you need to run all compiler checks (tests, lint, format) before committing. Detects whether TS or Rust code changed and runs the appropriate checks.
compiler-review
Review Rust port code for port fidelity, convention compliance, and error handling. Compares against the original TypeScript source.