Borrowing it
Nothing to install: this file belongs to BrainDAO/adk-ts. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/BrainDAO/adk-ts/main/.claude/commands/adk-ts-starter-sync.mdgit 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/commands/braindao/adk-ts/adk-ts-starter-sync)<a href="https://agentmods.dev/commands/braindao/adk-ts/adk-ts-starter-sync"><img src="https://agentmods.dev/badge/commands/braindao/adk-ts/adk-ts-starter-sync.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.1 | $0.00000 | $0.01271 |
| Opus 5 | $0.00000 | $0.00635 |
| Sonnet 5 | $0.00000 | $0.00254 |
| Haiku 4.5 | $0.00000 | $0.00127 |
Grade A, and why
adk-ts-starter-sync 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 8d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Synchronize shared boilerplate content across all starter template READMEs in apps/starter-templates/*/README.md.
Context
The starter template READMEs share ~70% identical content. When any shared section is updated in one template, all others must be updated to match. This command identifies drift and propagates updates.
Starter Templates
Discover all templates dynamically by listing directories in apps/starter-templates/*/README.md. Do NOT hardcode the list — new templates may be added at any time.
Workflow
Step 1: Read All Templates
Read all starter template READMEs in apps/starter-templates/*/README.md to understand the current state.
Step 2: Identify Shared Sections
These sections MUST be kept in sync (with only template-specific substitutions):
A. Quick Start Intro (identical)
Use either approach:
- **Recommended**: scaffold a fresh project with the ADK-TS CLI.
- **Alternative**: clone the repository and copy this template folder into your own project.
B. Prerequisites Base (identical base, template-specific extras appended)
### Prerequisites
- Node.js >=22.0
- pnpm
- {TEMPLATE_SPECIFIC_REQUIREMENT if any}
C. Step 1 Pattern (only template name and project name differ)
### Step 1: Create the project
` ` `bash
npx @iqai/adk-cli new --template {TEMPLATE_NAME} my-{template}
cd my-{template}
` ` `
D. Step 2: Install Dependencies (identical)
### Step 2: Install dependencies
` ` `bash
pnpm install
` ` `
E. Step 3: Configure Environment (identical)
### Step 3: Configure environment variables
` ` `bash
cp .env.example .env
` ` `
Required and optional values are documented in `.env.example`.
F. Test with ADK-TS CLI (verbatim identical)
## 🧪 Test with ADK-TS CLI
From your project directory, you can test agents without writing custom test scripts.
` ` `bash
# Option 1: Install ADK-TS CLI globally, then run
pnpm install -g @iqai/adk-cli
adk run
adk web
# Option 2: Use npx without global install
npx @iqai/adk-cli run
npx @iqai/adk-cli web
` ` `
- `adk run`: interactive terminal chat with your agent(s).
- `adk web`: launches a local server and opens the ADK-TS web interface.
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.
- 8d ago First seen · 181 lines · 0 tokens per session scan A c9964750ab56
adk-ts-starter-sync is a command published in the GitHub repository BrainDAO/adk-ts (119 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,271 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-30.
Other commands, from other repositories
lfe-session
You are acting as a senior framework architect helping improve the Library-First Engineering (LFE) framework. This is a META session — you are working ON the framework, not WITH it. Do NOT run the LFE pipeline (/lfe-boot, /lfe-architect, etc.) — those are for product repos that use LFE as a template.
lfe-compete
You are acting as a senior framework architect conducting a structured competitive analysis against Library-First Engineering (LFE). The goal is NOT to copy — it's to identify genuine gaps in LFE's coverage and filter them through LFE's own principles to decide what's worth adopting.
lfe-complexity-check
Inspector sub-skill. Analyses changed code for cyclomatic complexity, excessive nesting, oversized functions, and cognitive load indicators. Pure LLM reasoning — no external tooling. Writes .plans/checks/complexityfindings.md. Called by lfe-inspector when enabled in inspector-config.md.
lfe-dep-audit
Inspector sub-skill. Reviews dependency manifest files (package.json, requirements.txt, go.mod, Cargo.toml, pom.xml) changed in the current diff for risky version patterns and stale majors. Emits a human-run audit instruction rather than executing tools. Writes .plans/checks/depfindings.md. Called by lfe-inspector…
lfe-extract-domain
Conduct a "Day 0" interview with the founder to populate the project's domain-knowledge.md and CONTEXT.md. Use when the agent encounters an undocumented Black Box.
lfe-grill-with-docs
Deep alignment interview that challenges intent against the domain model, sharpens terminology, and writes back to CONTEXT.md and ADRs inline. Use at the start of any Major Change in the Architect sub-pipeline.