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 rules/freshworks-developers/fw-dev-tools/ai-actions-servergit 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.00000 | $0.02699 |
| Opus 5 | $0.00000 | $0.01350 |
| Sonnet 5 | $0.00000 | $0.00540 |
| Haiku 4.5 | $0.00000 | $0.00270 |
Grade A, and why
ai-actions-server 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 — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Actions server.js Patterns
Platform 3.0 pattern
const __formatError = (error, functionName) => {
console.error(`[${functionName}] Error:`, error);
let message;
try {
message = error.response ? JSON.parse(error.response) : error.message;
} catch {
message = error.response || error.message || 'Unknown error';
}
const parsedMessage = message instanceof Object ? JSON.stringify(message) : message;
return { status: error.status || 500, message: parsedMessage };
};
exports = {
actionName: async function(args) {
try {
const { param1 } = args;
const response = await $request.invokeTemplate('templateName', {
context: { param1: param1 },
body: JSON.stringify({ ... }) // if POST/PUT
});
const data = JSON.parse(response.response);
renderData(null, data);
} catch (error) {
renderData(__formatError(error, 'actionName'), null);
}
}
};
Error messages surfaced to users
Sanitize before renderData: Vendor error payloads may contain internal URLs, stack traces, tokens, or other sensitive data. Strip or map them to short, user-safe strings for the message passed to renderData; log the full error server-side only.
renderData Signature
renderData(error, data)
- Success:
renderData(null, data)— pass parsed response directly - Error:
renderData({ status, message }, null)
Rules
- Helper functions — Can be defined BEFORE exports
- $request.invokeTemplate() — Use only; never .post/.get/.put/.delete
- context — For path/query params:
context: { id: args.id } - body — For POST/PUT:
body: JSON.stringify(requestBody) - query — For GET query params:
query: { page: 1 } - Function name — Must match actions.json key exactly (case-sensitive)
Modular server layout
Keep server/server.js focused on SMI exports (exports = { ... }) and thin handlers. Move reusable logic into additional modules under server/services/, server/lib/, or similar, and require() them from server.js. This keeps complexity down and matches how npm dependencies are loaded from serverless code (Use external libraries).
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 · 320 lines · 0 tokens per session scan A a759e0948c46
ai-actions-server 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,699 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.
Other cursor rules, from other repositories
battle-tested-engineer
Battle-tested engineering judgment for code, refactors, tests, and frontend UI. Ultra-terse caveman style during code work.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.