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-readmegit 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-readme)<a href="https://agentmods.dev/rules/freshworks-developers/fw-dev-tools/ai-actions-readme"><img src="https://agentmods.dev/badge/rules/freshworks-developers/fw-dev-tools/ai-actions-readme.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.00324 |
| Opus 5 | $0.00000 | $0.00162 |
| Sonnet 5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
ai-actions-readme 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 4d 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.
What it actually says
AI Actions README Template
REQUIRED — every AI actions app must include a README.md at the app root. Absence of README.md is a blocking issue. Do not mark the app as complete without it.
Structure (Platform 3.0 AI Actions app)
# [App Name] AI Actions App
A Freshworks marketplace app that provides AI actions for [integration/service].
## Features
- **[Action 1]** - Brief description
- **[Action 2]** - Brief description
- **[Authentication]** - e.g., Bearer Token, OAuth
## Setup
1. Install the app in your Freshworks product
2. Configure credentials in app settings:
- [List iparams: API Key, Base URL, etc.]
## Actions Available
- `actionName1` - Description
- `actionName2` - Description
## Testing
cd <app-directory>
fdk run
Open https://localhost:10001/web/test, select type "actions", and test each action.
Rules
- Keep concise
- List all actions with function names
- Include setup steps for iparams
- Add testing instructions (fdk run, web/test)
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.
- 4d ago First seen · 48 lines · 0 tokens per session scan A e19ca526346e
ai-actions-readme is a cursor rule published in the GitHub repository freshworks-developers/fw-dev-tools (5 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 324 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
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.
family-instance-domain-actions
Family instance domain action implementation patterns.