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-requestsgit clone --depth 1 https://github.com/freshworks-developers/fw-dev-toolsWrote 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.
[](https://agentmods.dev/rules/freshworks-developers/fw-dev-tools/ai-actions-requests)<a href="https://agentmods.dev/rules/freshworks-developers/fw-dev-tools/ai-actions-requests"><img src="https://agentmods.dev/badge/rules/freshworks-developers/fw-dev-tools/ai-actions-requests.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.02618 |
| Opus 5 | $0.00000 | $0.01309 |
| Sonnet 5 | $0.00000 | $0.00524 |
| Haiku 4.5 | $0.00000 | $0.00262 |
Grade A, and why
ai-actions-requests 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 3d 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 — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Actions Request Templates
config/requests.json
{
"getResource": {
"schema": {
"method": "GET",
"host": "<%= iparam.api_base_url %>",
"path": "/api/v1/resources/<%= context.resource_id %>",
"headers": {
"Authorization": "Bearer <%= iparam.api_key %>",
"Accept": "application/json"
}
}
},
"createResource": {
"schema": {
"method": "POST",
"host": "<%= iparam.api_base_url %>",
"path": "/api/v1/resources",
"headers": {
"Authorization": "Bearer <%= iparam.api_key %>",
"Content-Type": "application/json"
}
}
},
"listResources": {
"schema": {
"method": "GET",
"host": "<%= iparam.api_base_url %>",
"path": "/api/v1/resources",
"headers": {
"Authorization": "Bearer <%= iparam.api_key %>",
"Accept": "application/json"
},
"query": {
"page": "<%= context.page %>",
"per_page": "<%= context.per_page %>"
}
}
},
"patchResource": {
"schema": {
"method": "PATCH",
"host": "<%= iparam.api_base_url %>",
"path": "/api/v1/resources/<%= context.resource_id %>",
"headers": {
"Authorization": "Bearer <%= iparam.api_key %>",
"Content-Type": "application/json"
}
}
},
"deleteResource": {
"schema": {
"method": "DELETE",
"host": "<%= iparam.api_base_url %>",
"path": "/api/v1/resources/<%= context.resource_id %>",
"headers": {
"Authorization": "Bearer <%= iparam.api_key %>",
"Accept": "application/json"
}
}
}
}
Substitution
| Variable | Use |
|---|---|
<%= iparam.name %> |
Installation parameters |
<%= context.name %> |
Runtime args from server.js |
<%= access_token %> |
OAuth (with options.oauth) |
Rules
- Host: FQDN only (api.example.com) — no protocol, no path
- Path: Must start with
/ - Syntax:
<%= %>(ERB) — never{{ }} - Protocol: Optional; use
"protocol": "https"if needed
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.
- 3d ago First seen · 306 lines · 0 tokens per session scan A e1b3c1c587f6
ai-actions-requests is a cursor rule published in the GitHub repository freshworks-developers/fw-dev-tools (5 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,618 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.