platform3-modules-locations

A reference for Freshworks Platform 3.0 modules and locations. Modules group features by product area, while locations specify where an app appears, such as a ticket sidebar or full-page app.

In plain words
What is it for?
Use it to choose product modules, configure app locations, and define requests, functions, and events in a Freshworks app manifest.
Why use it?
It removes guesswork when writing the manifest, so the app uses the required module structure and declares its permissions and events correctly.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/freshworks-developers/fw-dev-tools/platform3-modules-locations
Clone the repo
git clone --depth 1 https://github.com/freshworks-developers/fw-dev-tools
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 2,328 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.02328
Opus 5 $0.00000 $0.01164
Sonnet 5 $0.00000 $0.00466
Haiku 4.5 $0.00000 $0.00233

Measured 2d ago against content hash 0ae438a88c47, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

platform3-modules-locations 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.

skills/fw-app-dev/rules/platform3-modules-locations.mdc · 405 lines

How it starts

The opening of the file, as written. The whole thing — 405 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Platform 3.0 Modules and Locations

Module Structure

Platform 3.0 uses a modules structure instead of the legacy product structure:

{
  "platform-version": "3.0",
  "modules": {
    "common": {
      /* Global locations and config */
    },
    "product_module": {
      /* Product-specific locations */
    }
  }
}

Key Rules:

  1. ✅ Must include at least ONE product module (even if empty: {})
  2. common module is for global placeholders (full_page_app, cti_global_sidebar)
  3. ✅ Product modules define product-specific locations
  4. ✅ Must declare requests, functions, and events in manifest

Freshdesk Modules

Available Modules

  • support_ticket - Ticket features
  • support_contact - Contact features
  • support_company - Company features
  • support_agent - Agent features
  • support_email - Email features
  • support_portal - Portal features

support_ticket Locations

Common Placeholders (in modules.common.location):

  • full_page_app - Full-page standalone app
  • cti_global_sidebar - Global CTI sidebar

Module Placeholders (in modules.support_ticket.location):

  • ticket_sidebar - Ticket details page sidebar
  • ticket_requester_info - Requester information section
  • ticket_top_navigation - Top navigation bar in ticket
  • ticket_background - Background app (no UI, intercept events)
  • time_entry_background - Background for time entries
  • ticket_attachment - Attachment section
  • ticket_conversation_editor - Conversation editor
  • new_ticket_requester_info - New ticket requester info
  • new_ticket_background - New ticket background

Example: Freshdesk Ticket Sidebar App

{
  "platform-version": "3.0",
  "modules": {
    "common": {
      "location": {
        "full_page_app": {
          "url": "index.html",
          "icon": "styles/images/icon.svg"
        }
      },
      "requests": {
        "externalApi": {}
      },
      "functions": {
        "smiMethod": {}
      }
    },
    "support_ticket": {
      "location": {
        "ticket_sidebar": {
          "url": "ticket_sidebar.html",
          "icon": "styles/images/icon.svg"
        },
        "ticket_background": {
          "url": "ticket_background.html"
        }
      },
      "events": {
        "onTicketCreate": {
          "handler": "onTicketCreateHandler"
        }
      }
    }
  },
  "engines": {
    "node": "24.11.0",
    "fdk": "10.0.1"
  }
}

Read the full file on GitHub · 405 lines

Changes

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.

  1. 2d ago First seen · 405 lines · 0 tokens per session scan A 0ae438a88c47

Subscribe to this mod's changes

platform3-modules-locations is a cursor rule published in the GitHub repository freshworks-developers/fw-dev-tools (5 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,328 tokens. 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-31.