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/async-patternsgit 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.01594 |
| Opus 5 | $0.00000 | $0.00797 |
| Sonnet 5 | $0.00000 | $0.00319 |
| Haiku 4.5 | $0.00000 | $0.00159 |
Grade A, and why
async-patterns 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 yesterday.
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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Async/Await Patterns for FDK Validation
When to use: fdk validate shows async-related errors
Common Async Errors
Error 1: Async without await
Lint Error: Async function has no 'await' expression
Fix: Remove async keyword OR add actual await
// [INVALID] WRONG: async without await
exports = {
onAppInstallHandler: async function() {
console.log('Installed');
}
};
// [VALID] CORRECT: Remove async
exports = {
onAppInstallHandler: function() {
console.log('Installed');
}
};
// [VALID] CORRECT: Add await
exports = {
onAppInstallHandler: async function() {
await $db.set('installed', { timestamp: Date.now() });
console.log('Installed');
}
};
Error 2: Async Variable Scoping (Frontend)
Warning: Async function may cause race conditions in frontend initialization
Fix: Use IIFE pattern
// [INVALID] WRONG: Top-level async causes race conditions
async function init() {
const client = await app.initialized();
// ... rest of code
}
init();
// [VALID] CORRECT: IIFE pattern
(async function() {
const client = await app.initialized();
// ... rest of code
})();
Error 3: Unhandled Promise Rejection
Warning: Expected rejection to be handled
Fix: Wrap in try/catch
// [INVALID] WRONG: No error handling
exports = {
fetchData: async function() {
const result = await $request.invokeTemplate('api', {});
return result;
}
};
// [VALID] CORRECT: Try/catch wrapper
exports = {
fetchData: async function() {
try {
const result = await $request.invokeTemplate('api', {});
return { success: true, data: result };
} catch (e) {
console.error('API call failed:', e.message);
return { success: false, error: e.message };
}
}
};
Frontend Async Patterns
Pattern 1: App Initialization (IIFE)
// [VALID] CORRECT: Standard frontend pattern
(async function() {
const client = await app.initialized();
document.getElementById('btn').addEventListener('fwClick', async () => {
try {
const response = await client.request.invoke('getData', {});
displayResult(response);
} catch (e) {
showError(e.message);
}
});
})();
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.
- yesterday First seen · 260 lines · 0 tokens per session scan A eb49f58257da
async-patterns is a cursor rule published in the GitHub repository freshworks-developers/fw-dev-tools (5 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,594 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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.