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 jotform/mcp-server --skill jotform-formsgit clone --depth 1 https://github.com/jotform/mcp-serverWrote 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/jotform/mcp-server/jotform-forms)<a href="https://agentmods.dev/skills/jotform/mcp-server/jotform-forms"><img src="https://agentmods.dev/badge/skills/jotform/mcp-server/jotform-forms/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/jotform/mcp-server/jotform-forms"><img src="https://agentmods.dev/badge/skills/jotform/mcp-server/jotform-forms.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.00082 | $0.00697 |
| Opus 5.5 | $0.00033 | $0.00279 |
| Sonnet 5.5 | $0.00016 | $0.00139 |
| Haiku 4.5 | $0.00008 | $0.00070 |
Grade A, and why
jotform-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 2d 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jotform forms
Use tools from the jotform connector. When another connector exposes the same short tool name, choose the tool that belongs to jotform.
Do the task
- Treat the connected server's current tool definitions as the contract. If the connector is unavailable, name the connection the user needs. Never ask for a password or token in chat.
- For an existing form, use the form ID the user supplied or this connector's
search. Ask which form they mean only when more than one match is plausible. Do not create a new form to satisfy an edit. - Use
create_formfor a new form,edit_formfor changes, anddisplay_formfor a preview. Usefetch,list_submissions, oranalyze_submissionsfor retrieval and analysis. Callcreate_submissiononly when the user asked to submit data and the required values are known. - Put the user's requirements in
description. Forcreate_form, useworkspace_type: "personal"andteam_id: ""unless the user asks for a team. Resolve a named team with this connector'sget_teams, then pass its numeric ID andworkspace_type: "team". Follow the live schema for every other tool. - Pass a file only when the live schema has an input for it. Do not invent file IDs or download URLs. If the file cannot be supplied, say so and ask for the form content another way.
A create or edit that is still running
Do not call create_form or edit_form again to check progress. If the response says the work is still running (for example url: "in_progress"), keep the returned form ID, including related_asset.asset_id when it is present, and call this connector's fetch.
- If
metadata.build_statusisprocessing, wait formetadata.poll_after_secondswhen that value is present, then fetch the same ID. If no retry timing is given, report that the operation is pending. - If the status is
completed, summarize the verified result. - If it is
awaiting_confirmation, show the question and choices and wait for the user's answer before another edit. - If it is
failed, stop and explain the reported failure. - If the response has no status and no ID, say the outcome is unknown. Do not start another creation.
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.
- 2d ago First seen · 33 lines · 82 tokens per session scan A ea21c02fae56
jotform-forms is a skill published in the GitHub repository jotform/mcp-server (29 stars, last pushed 3d ago), licensed MIT. It adds 82 tokens to every session and 697 once invoked, about $0.0003 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-10-23.
Other skills, from other repositories
aident-skill
Use Aident Loadout to connect your AI agents to 1,000+ real-world apps and tools like Gmail, Slack, Linear, Notion, Firecrawl, and Fal, unlock 27,000+ executable actions, and track full audit history so your agents can get real work done reliably.
using-powerups
Use when starting work in a repository with Agent Powerups installed, when a task may match a reusable local skill, command, workflow, hook recipe, AGENTS.md template, or MCP feature.
context-minimization
Use when a task runs long and the context window is filling -- large files are being read whole, command output is flooding the transcript, or responses are getting verbose and slow.
save-handoff
Save a concise handoff summary only when the user explicitly requests it. Use this for resumable progress notes in generic agent environments where a real session importer is not guaranteed.
no-fluff
Ultra-compressed communication mode. Cuts token usage 75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "no fluff", "be concise", "use less tokens", or similar.
repo-map
Use when the task is to understand an unfamiliar codebase, locate key entry points, or summarize architecture before editing.