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 agentmods add agents/freshworks-developers/fw-dev-tools/app-security-scannergit clone --depth 1 https://github.com/freshworks-developers/fw-dev-toolsWhat 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 | $0.00051 | $0.01570 |
| Opus 5 | $0.00026 | $0.00785 |
| Sonnet 5 | $0.00010 | $0.00314 |
| Haiku 4.5 | $0.00005 | $0.00157 |
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.
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:
- Scan the apps folder at
apps/in the workspace root - Ask the user which apps to scan (all, specific range, or specific apps)
- Run security analysis on each app
- Generate comprehensive report
Security Checks
Critical Security Issues
-
Credential Exposure
- API keys hardcoded in code (not using
args.iparams) - Secrets in frontend JavaScript files
- Tokens logged to console
- Credentials in comments
- API keys hardcoded in code (not using
-
Injection Vulnerabilities
- Unsanitized user input in API calls
- Dynamic code execution (
eval,new Function) - Template injection in request templates
- SQL/NoSQL injection patterns
-
Authentication Issues
- Missing authentication headers
- Weak auth patterns (plain text passwords)
- OAuth misconfigurations
- API key exposure in client-side code
-
Data Exposure
- Sensitive data logged (
console.logwith PII) - Error messages exposing internal details
- Debug code in production
- Sensitive data logged (
Code Quality Checks
-
Platform 3.0 Compliance
- Using
$request.invokeTemplate()(not$request.get/post) - Manifest has
"platform-version": "3.0" - Using
modulesnotproduct - No
whitelisted-domains
- Using
-
Best Practices
- Async functions have
awaitexpressions - Proper error handling (try/catch blocks)
- No unused variables/parameters
- Helper functions after exports block
- Async functions have
-
File Structure
icon.svgexists for frontend appsiparams.jsonexists- 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*\{/
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 · 220 lines · 51 tokens per session scan A d88da4fed44c
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.
Other agents, from other repositories
base-template-generator
Use this agent when you need to create foundational templates, boilerplate code, or starter configurations for new projects, components, or features. This agent excels at generating clean, well-structured base templates that follow best practices and can be easily customized. Examples: Context: User needs to start a…
governance-specialist
Enforces engineering standards and code quality policies. Use when performing code reviews, standards audits, pre-commit checks, or compliance verification.
plan-review-specialist
Multi-perspective plan review specialist that coordinates VP Product, VP Engineering, and VP Design perspectives to identify blockers, anti-patterns, conflicts, and regressions. Use when reviewing implementation plans, design docs, or wave plans.
agent-capabilities
Matrix of agent capabilities and their specializations.
agent-coordination
Coordination patterns for multi-agent collaboration.
agent-spawning
Guide to spawning agents with Claude Code's Task tool.