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-appsgit 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-apps)<a href="https://agentmods.dev/skills/jotform/mcp-server/jotform-apps"><img src="https://agentmods.dev/badge/skills/jotform/mcp-server/jotform-apps/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-apps"><img src="https://agentmods.dev/badge/skills/jotform/mcp-server/jotform-apps.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.00046 | $0.00609 |
| Opus 5.5 | $0.00018 | $0.00244 |
| Sonnet 5.5 | $0.00009 | $0.00122 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
jotform-apps 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.
What it actually says
Jotform Apps
Use tools from the jotform-apps connector. Its search and fetch operate on apps. Do not use them for regular forms or Sign documents.
- 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 app, use the
app_idthe user supplied or this connector'ssearch. Usefetchfor its details. Do not create a new app to satisfy an edit. - Use
create_appwithdescriptionfor a new app. State the pages, purpose, and content the user supplied. Useedit_appwithapp_idandinstructionsfor a change. Do not add aform_idargument the schema does not define. - To embed an existing form, put its verified ID and returned URL in
descriptionorinstructions, and say to reuse that form rather than create a replacement. Include only content the user authorized for the app. Keep private submissions, contracts, and personal signing links out of app content. - For
create_app, personal workspace usesworkspace_type: "personal"andteam_id: null. A team workspace needs the numeric ID from this connector'sget_teamsandworkspace_type: "team". Do not copy the empty-string team ID used by the forms connector. Apply workspace arguments on other tools only when the live schema has them. - For a
processingresponse, keep the returned app ID (includingrelated_asset.asset_idwhen present) and call this connector'sfetch. Ifmetadata.build_statusisprocessing, wait formetadata.poll_after_secondswhen it is present. Stop on completion, failure, or a confirmation question. If timing or status is missing, report the app as pending. Do not call creation or editing again to poll. - Confirm the requested outcome from the returned app details and the rendered preview. If those results do not show the embedded form ID, say reuse is unverified and ask the user to check the form in the preview. If a duplicate form appeared, report it. Do not delete assets or start another app to compensate.
Apply only the changes the user asked for, and leave unrelated pages in place. Do not infer that an app is published from a successful draft. Report the sharing state and URL the service returns.
After an uncertain response or timeout, inspect the existing app before retrying a write. If authentication or permissions fail, keep the known app and name the step that failed. Finish with a short summary and a verified link or preview.
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 · 21 lines · 46 tokens per session scan A def2bce14996
jotform-apps is a skill published in the GitHub repository jotform/mcp-server (29 stars, last pushed 3d ago), licensed MIT. It adds 46 tokens to every session and 609 once invoked, about $0.0002 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.