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/baseapiclientgit clone --depth 1 https://github.com/altaidevorg/rules-for-aiWrote 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/altaidevorg/rules-for-ai/baseapiclient)<a href="https://agentmods.dev/rules/altaidevorg/rules-for-ai/baseapiclient"><img src="https://agentmods.dev/badge/rules/altaidevorg/rules-for-ai/baseapiclient.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.04420 |
| Opus 5 | $0.00000 | $0.02210 |
| Sonnet 5 | $0.00000 | $0.00884 |
| Haiku 4.5 | $0.00000 | $0.00442 |
Grade A, and why
baseapiclient 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 — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chapter 8: BaseApiClient
In Chapter 7: Transformers (t_ functions), we saw how the google-genai SDK uses internal helper functions to convert user-friendly data types into the structured formats required by the API. Once the data is correctly formatted, something needs to actually send it over the network, handle authentication, and process the response. This chapter dives into that core component: the BaseApiClient.
Motivation and Use Case
Directly interacting with HTTP APIs involves numerous low-level details: correctly formatting URLs, setting headers (like Content-Type, User-Agent, and authorization tokens), serializing request bodies (usually to JSON), sending the request using an HTTP library, handling potential network errors, deserializing the response body, and checking the response status code. Furthermore, authentication requires managing API keys or obtaining and refreshing access tokens from credentials (like Google Cloud ADC). Different backends (Gemini vs. Vertex AI) might use different base URLs or API versions.
Managing all this complexity within each high-level SDK function (like Models.generate_content) would lead to massive code duplication and make the SDK difficult to maintain.
The BaseApiClient solves this by encapsulating all the core logic for API communication. It acts as the central engine that higher-level components, like the API Modules (Models, Chats, Files, Tunings, Caches, Batches, Operations, Live), rely on to execute their tasks. It abstracts away the complexities of HTTP, authentication, endpoint differences, and basic error checking.
Central Use Case: Although you, as an SDK user, will interact with the Client and its API modules, understanding BaseApiClient is crucial for grasping the SDK's internal architecture. When you call a method like client.models.generate_content(...):
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 · 312 lines · 0 tokens per session scan A 03c51517fe52
baseapiclient is a cursor rule published in the GitHub repository altaidevorg/rules-for-ai (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,420 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.