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/willdady/platypus/form-conventionsnpx skills add willdady/platypus --skill form-conventionsgit clone --depth 1 https://github.com/willdady/platypusWrote 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/willdady/platypus/form-conventions)<a href="https://agentmods.dev/skills/willdady/platypus/form-conventions"><img src="https://agentmods.dev/badge/skills/willdady/platypus/form-conventions.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.1 | $0.00051 | $0.00778 |
| Opus 5 | $0.00026 | $0.00389 |
| Sonnet 5 | $0.00010 | $0.00156 |
| Haiku 4.5 | $0.00005 | $0.00078 |
Grade A, and why
form-conventions 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 4d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Form Conventions
Where a save lands
One rule covers every form: a save returns the user to the entity's home, and only leaves the page when the form has no home to return to. Which of the two applies falls out of the entity's shape in the route tree:
| Shape | The form is… | On save | Examples |
|---|---|---|---|
| Collection member | the entity's page, reached from a list | go to list | Agents, Blueprints, Skills, Triggers, MCP, Providers, Webhooks, Workspace Context |
| Entity sub-page | a settings/ child of a page the entity owns |
stay | Boards, Dashboards |
| Singleton | one per Workspace/Org/account, so there is no list | stay | Sandbox, Organization, Workspace |
| Dialog or inline | not a page at all | stay | Members, Invitations, Global Context, everything in Chat |
Read the shape off apps/frontend/app. settings/agents/[agentId] renders
the agent edit form — an agent has no detail page, so leaving the form means
returning to settings/agents. A board does have a page, and its form lives
at boards/[boardId]/settings, so saving keeps you there.
Staying means mutate() (or router.refresh()) plus a toast. Never
router.push to the page you are already on.
Creating always navigates — to the new entity where it has a page of its own, otherwise to the list it now belongs to.
Deleting always navigates away from whatever it destroyed, whatever the shape: to the list for a collection member, to the parent otherwise.
A list is wherever the list actually renders, not a route that looks like one.
Triggers navigate to the Workspace home because that is where the trigger list
lives; there is no triggers/ page.
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.
- 4d ago First seen · 64 lines · 51 tokens per session scan A 3d9a64784dac
form-conventions is a skill published in the GitHub repository willdady/platypus (72 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 778 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-01.
Other skills, from other repositories
ideation
Generate project ideas through creative constraints. Use when the user says 'I want to build something', 'give me a project idea', 'I'm bored', 'what should I make', 'inspire me', or any variant of 'I have tools but no direction'. Works for code, art, hardware, writing, tools, and anything that can be made.
mcp-servers
Add, remove, configure, and troubleshoot MCP (Model Context Protocol) servers. Use when the user wants to connect external tools, manage MCP server lifecycle, or debug MCP connectivity issues.
slacrawl
Archive and search Slack workspace messages, threads, and channels via the slacrawl CLI. Supports API sync, Slack export ZIP import, local desktop cache import, and full-text search.
apple-notes
Manage Apple Notes via the memo CLI on macOS (create, view, search, edit).
obsidian
Read, search, and create notes in the Obsidian vault.
commonly
You are a member of a Commonly workspace — a shared space where humans and AI agents from any origin collaborate in pods (chat rooms with memory). Use this whenever you are connected to Commonly via the commonly MCP tools: to read what's happening, post, remember things across sessions, react, DM other agents, and…