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.
git clone --depth 1 https://github.com/BrainDAO/adk-tsWrote 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/braindao/adk-ts/aim)<a href="https://agentmods.dev/rules/braindao/adk-ts/aim"><img src="https://agentmods.dev/badge/rules/braindao/adk-ts/aim/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/braindao/adk-ts/aim"><img src="https://agentmods.dev/badge/rules/braindao/adk-ts/aim.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00222 | $0.00222 |
| Opus 5.5 | $0.00089 | $0.00089 |
| Sonnet 5.5 | $0.00044 | $0.00044 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
aim 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 1mo 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
Project Aim
Python to TypeScript Port
The aim of this project is to port the adk-python implementation to TypeScript (adk-ts). When porting code:
- Refer to the original implementation of the Python files
- Replicate their logic faithfully in TypeScript
- Ensure the core functionality remains identical
- Maintain the same logical structure and components
Requirements
-
Logic Preservation: The TypeScript implementation MUST maintain the same logical flow and behavior as the Python version.
-
Component Naming: Core components should maintain conceptual naming parity with the Python version.
-
Architecture: Follow the same architectural patterns and separation of concerns as the Python implementation.
-
File Organization: Mirror the Python project's organizational structure where appropriate, adapting to TypeScript conventions.
Implementation Notes
- Use TypeScript's type system to enhance the original Python implementation
- Apply language-specific best practices for TypeScript while preserving the original logic
- Adapt Python-specific patterns to TypeScript equivalents where direct ports aren't possible
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.
- 1mo ago First seen · 31 lines · 222 tokens per session scan A 5342689a951c
aim is a cursor rule published in the GitHub repository BrainDAO/adk-ts (119 stars, last pushed 3mo ago), licensed MIT. It adds 222 tokens to every session, about $0.0009 per session on Opus 5.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-30.
Other cursor rules, from other repositories
windsurfrules
Below is an example TypeScript/Node.js folder structure replicating the Python package's layout. Each subfolder matches the Python counterpart (agent, agents, knowledge, etc.). All "LLM" or "litellm" references are replaced by aisdk usage.
igniter-patterns
This guide provides a COMPLETE, ACCURATE, and MANDATORY reference for creating controllers and actions in Igniter.js. It incorporates established architectural patterns, coding best practices, and lessons learned from real-world implementations, ensuring strict adherence for all future development.
nestjs-best-practices
../../.claude/rules/nestjs-best-practices.md.
general-rule
Cursor rule "general-rule" from vinhnx/vtchat, covering development guidelines, tech stack & project overview, package management, code style and ui/ux design principles.
nextjs15-react19-vercelai-tailwind
Next.js 15 React 19 Vercel Tailwind.
all-ts
../../.claude/rules/all-ts.md.