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/altaidevorg/rules-for-ai/chat___asyncchatgit clone --depth 1 https://github.com/altaidevorg/rules-for-aiWhat 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.00025 | $0.03328 |
| Opus 5 | $0.00013 | $0.01664 |
| Sonnet 5 | $0.00005 | $0.00666 |
| Haiku 4.5 | $0.00003 | $0.00333 |
Grade A, and why
chat___asyncchat 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 — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chapter 4: Chat / AsyncChat
In Chapter 3: API Modules (Models, Chats, Files, Tunings, Caches, Batches, Operations, Live), we saw how the SDK organizes functionalities into modules like Models. While client.models.generate_content is powerful, using it directly for conversations requires manually managing the history: appending the user's message, sending the full history, and then appending the model's response. This chapter introduces Chat and AsyncChat, abstractions designed to simplify this common pattern.
Motivation and Use Case
Building conversational AI requires maintaining the context of the interaction over multiple turns. Sending only the latest user message to the model results in stateless, disconnected responses. The model needs the preceding dialogue to understand the context and respond coherently. Manually constructing the list[Content] history for every API call can be repetitive and error-prone, especially when handling potential errors or invalid responses from the model.
The Chat (and its asynchronous counterpart AsyncChat) provides a stateful object that automatically manages this conversation history. You send a message, and the Chat object handles appending it to the history, calling the underlying Models module with the full context, and storing the model's response, ready for the next turn.
Central Use Case: Imagine creating a simple chatbot that remembers previous interactions.
# Assuming 'client' is configured (e.g., using genai.Client(api_key=...))
from google import genai
from google.genai import types
# 1. Create a Chat session using the 'chats' module factory
# Note: client.chats is a factory for Chat instances
chat = client.chats.create(model='gemini-1.5-flash') # Or your preferred model
# 2. Send the first message
response1 = chat.send_message("Hello! My name is Alex.")
print(f"AI: {response1.text}")
# 3. Send the second message - the Chat object remembers the first turn
response2 = chat.send_message("What is my name?")
print(f"AI: {response2.text}") # The AI should know your name is Alex
# 4. Inspect the history managed by the Chat object
print("\n--- Chat History ---")
# Use get_history(curated=True) for only valid turns sent to the model
for content in chat.get_history(curated=False): # Shows all turns
print(f"{content.role.capitalize()}: {content.parts[0].text}")
This example shows how chat.send_message handles the history. The second call automatically includes the context ("Hello! My name is Alex." and the AI's first response) when generating the answer to "What is my name?".
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 · 274 lines · 25 tokens per session scan A 03024fea65f5
chat___asyncchat is a cursor rule published in the GitHub repository altaidevorg/rules-for-ai (2 stars, last pushed 1y ago), licensed MIT. It adds 25 tokens to every session and 3,328 once invoked, about $0.0001 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 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.