fw-publish

fw-publish is a skill for Claude Code from freshworks-developers/fw-dev-tools. It costs 170 tokens per session (8,086 once invoked), scanned C, original, MIT.

A publishing workflow for Freshworks Platform 3.0 custom apps, including validation, packaging, uploading, and marketplace submission or updates.

In plain words
What is it for?
Use it to prepare an app archive, verify its marketplace compliance, confirm the Developer JWT matches the app’s products, and publish a test listing.
Why use it?
It brings the required review, product-module checks, and publishing steps into one process, while identifying network restrictions that can prevent upload.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths; mentions Claude Code.

Part of the fw-publish plugin — 1 skill shipped together

Good fit Use it to prepare an app archive, verify its marketplace compliance, confirm the Developer JWT matches the app’s products, and publish a test listing.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/freshworks-developers/fw-dev-tools/fw-publish
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.

Any agent
npx skills add freshworks-developers/fw-dev-tools --skill fw-publish
Clone the repo
git clone --depth 1 https://github.com/freshworks-developers/fw-dev-tools

Made for: Claude Code.

Or install fw-publish, the plugin that ships this one along with the rest of its 1 skill.

Wrote 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.

agentmods badge for fw-publish

README.md
[![agentmods](https://agentmods.dev/badge/skills/freshworks-developers/fw-dev-tools/fw-publish.svg)](https://agentmods.dev/skills/freshworks-developers/fw-dev-tools/fw-publish)
Your own site
<a href="https://agentmods.dev/skills/freshworks-developers/fw-dev-tools/fw-publish"><img src="https://agentmods.dev/badge/skills/freshworks-developers/fw-dev-tools/fw-publish.svg" alt="Measured on agentmods" height="20"></a>
Per session 170 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 8,086 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00170 $0.08086
Opus 5 $0.00085 $0.04043
Sonnet 5 $0.00034 $0.01617
Haiku 4.5 $0.00017 $0.00809

Measured today against content hash 38dccc8ff91e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade C, and why

fw-publish scanned grade C with 2 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 today.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/repack-app-zip.sh, scripts/upload-app.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf /tmp/fw-repack && mkdir -p /tmp/fw-repack && unzip -q -o 'dist/<app>.zip' -d /tmp/fw-repack

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

**Sandbox / agent egress:** Publish **does not work** in **sandbox** (or equivalent) modes that block MCP traffic to `https://mcp.freshworks.dev/mcp` or outbound HTTPS (including **`curl`** PUT to the app-upload URL). So
skills/fw-publish/SKILL.md · 410 lines

How it starts

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

Publish (Platform 3.0 custom app)

MANDATORY PREREQUISITE: Run fw-review skill before publishing to ensure marketplace compliance. The review checks iparams, frontend files, security patterns, and generates a structured audit report. Do not proceed with publishing until review passes.

Goal: Take any Platform 3.0 app folder (with manifest.json), produce dist/*.zip, and publish it to the Freshworks Marketplace via MCP tools. Currently, only test state is supported.

Sandbox / agent egress: Publish does not work in sandbox (or equivalent) modes that block MCP traffic to https://mcp.freshworks.dev/mcp or outbound HTTPS (including curl PUT to the app-upload URL). Some cloud or CI agent runtimes send HTTPS through a proxy, gateway, or assumed IAM role that is not allowed to PUT to the Marketplace app-upload bucket (fa-*-app-uploads…): S3 returns 403 / AccessDenied even when the presigned URL is valid. Do not run this playbook in a sandboxed agent or restricted shell. If the user’s client offers sandbox vs full network access, choose non-sandbox / allow network for publish. On 403 PUT after following step 8 exactly, ask the user to run the same script command on their local machine (see step 8).

Agent playbook (MCP tools)

Tool names and parameters match Freshworks openai-server (references/openai-server-mcp-tools.md). Hosted MCP: https://mcp.freshworks.dev/mcp.

1. Auth token preflight (MUST be step 1)

Before any MCP tool call, verify that the MCP publish tools are available and authenticated:

  • Attempt to call list_custom_apps (optionally {} or { "page": 1, "perPage": 10 }). Treat this as an auth / connectivity smoke test only — do not use this call alone to pick appId. At publish time (step 6), you will ask new vs existing again and, for existing, call list_custom_apps for developer selection.
  • If the call succeeds, auth is confirmed — proceed to step 2.
  • If tools are not available or the call returns an auth error, determine which case applies:

Read the full file on GitHub · 410 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. today Changed 38dccc8ff91e
  2. 8d ago First seen · 410 lines · 170 tokens per session scan C bcf83ee588bb

Subscribe to this mod's changes

fw-publish is a skill published in the GitHub repository freshworks-developers/fw-dev-tools (5 stars, last pushed today), licensed MIT. It adds 170 tokens to every session and 8,086 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.