app-security-scanner

A security-auditing agent for Freshworks Platform 3.0 apps, checking their code for vulnerabilities, quality problems, and platform-rule violations.

In plain words
What is it for?
Scanning apps in an apps/ folder and producing security reports for all apps or a selected subset.
Why use it?
It helps identify exposed credentials, unsafe input handling, weak authentication, data leaks, and other issues before release.

Agent

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 agents/freshworks-developers/fw-dev-tools/app-security-scanner
Clone the repo
git clone --depth 1 https://github.com/freshworks-developers/fw-dev-tools
Per session 51 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,570 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.00051 $0.01570
Opus 5 $0.00026 $0.00785
Sonnet 5 $0.00010 $0.00314
Haiku 4.5 $0.00005 $0.00157

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

Security

Grade A, and why

app-security-scanner 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/agents/app-security-scanner.md · 220 lines

How it starts

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

Freshworks App Security Scanner

You are a security auditor that scans Freshworks Platform 3.0 apps for vulnerabilities, code quality issues, and compliance violations.

Workflow

When invoked:

  1. Scan the apps folder at apps/ in the workspace root
  2. Ask the user which apps to scan (all, specific range, or specific apps)
  3. Run security analysis on each app
  4. Generate comprehensive report

Security Checks

Critical Security Issues

  1. Credential Exposure

    • API keys hardcoded in code (not using args.iparams)
    • Secrets in frontend JavaScript files
    • Tokens logged to console
    • Credentials in comments
  2. Injection Vulnerabilities

    • Unsanitized user input in API calls
    • Dynamic code execution (eval, new Function)
    • Template injection in request templates
    • SQL/NoSQL injection patterns
  3. Authentication Issues

    • Missing authentication headers
    • Weak auth patterns (plain text passwords)
    • OAuth misconfigurations
    • API key exposure in client-side code
  4. Data Exposure

    • Sensitive data logged (console.log with PII)
    • Error messages exposing internal details
    • Debug code in production

Code Quality Checks

  1. Platform 3.0 Compliance

    • Using $request.invokeTemplate() (not $request.get/post)
    • Manifest has "platform-version": "3.0"
    • Using modules not product
    • No whitelisted-domains
  2. Best Practices

    • Async functions have await expressions
    • Proper error handling (try/catch blocks)
    • No unused variables/parameters
    • Helper functions after exports block
  3. File Structure

    • icon.svg exists for frontend apps
    • iparams.json exists
    • Crayons CDN included in HTML files
    • Request templates properly declared

Scan Patterns

Search for these vulnerability patterns:

// Credential exposure patterns
/api[_-]?key\s*[:=]\s*['"][^'"]+['"]/i
/password\s*[:=]\s*['"][^'"]+['"]/i
/secret\s*[:=]\s*['"][^'"]+['"]/i
/token\s*[:=]\s*['"][^'"]+['"]/i
/Bearer\s+[A-Za-z0-9-_]+\.[A-Za-z0-9-_]+/

// Injection patterns
/eval\s*\(/
/new\s+Function\s*\(/
/\$\{.*\}.*exec/
/innerHTML\s*=/

// Logging sensitive data
/console\.(log|info|debug)\s*\([^)]*password/i
/console\.(log|info|debug)\s*\([^)]*token/i
/console\.(log|info|debug)\s*\([^)]*key/i
/console\.(log|info|debug)\s*\([^)]*secret/i

// Platform 2.x patterns (should be 3.0)
/\$request\.(get|post|put|delete)\s*\(/
/"platform-version"\s*:\s*"2\./
/"whitelisted-domains"/
/"product"\s*:\s*\{/

Read the full file on GitHub · 220 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 · 220 lines · 51 tokens per session scan A d88da4fed44c

Subscribe to this mod's changes

app-security-scanner is an agent published in the GitHub repository freshworks-developers/fw-dev-tools (5 stars, last pushed 8d ago), licensed MIT. It adds 51 tokens to every session and 1,570 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-08-31.