agent-toolkit-cli 1.0.3__py3-none-any.whl

agent_toolkit_cli-1.0.3.data/data/agent_toolkit/data/loops/oss-pr-monitor/loop.yaml

@@ -0,0 +1,85 @@
+# Loop starter: oss-pr-monitor
+# An L2 loop that monitors open PRs across a multi-repo OSS ecosystem.
+# Cadence: daily. Cost: high (scales with repo count).
+# Designed for maintainers managing 20-50 repos.
+#
+# Usage:
+#   ./bin/loop init oss-pr-monitor --pack packs/my-ecosystem.yaml
+
+name: oss-pr-monitor
+description: "Monitor open PRs across OSS ecosystem repos and take action (L2, daily)"
+tier: L2
+cadence: 1d
+resumable: true
+
+goal: |
+  Review all open PRs across all configured repos. For each PR:
+  - Dependabot PR with passing CI → merge
+  - Dependabot PR with dirty state → close (it will regenerate)
+  - Human PR with CI failures → report with diagnosis
+  - Human PR with conflicts → report, do not close
+  - Any security concern → escalate
+
+allowlist:
+  - merge
+  - close
+  - comment
+  - label
+deny:
+  - approve
+  - force-push
+  - push-to-main
+  - delete-branch
+
+exit_conditions:
+  - goal_met
+  - budget_exhausted
+  - human_escalation
+
+budget:
+  max_tokens: 300000
+  max_runs_per_day: 1
+  max_wall_seconds: 1800
+
+verifier: agent-toolkit-code-reviewer
+
+request: |
+  You are running the OSS PR Monitor loop.
+
+  **Resumability (read first):**
+  Read loops/oss-pr-monitor/STATE.md. If `last_processed_repo` is set, skip all
+  repos before that name. After processing each repo, update STATE.md:
+    last_processed_repo: <owner>/<repo>
+  On successful completion, clear last_processed_repo and set last_run_status: success.
+
+  **Style rules:**
+  - Never @mention anyone. Never leave AI-looking comments.
+  - If the right action is obvious → do it silently.
+  - If not obvious → skip and note in report.
+  - The report is reviewed by a human — that is where pending items get discussed.
+
+  **Step 1 — List open PRs**
+  For each repo in your pack/config:
+    gh api "repos/$repo/pulls?state=open&per_page=50" \
+      --jq '.[] | "\(.number)|\(.title)|\(.user.login)|\(.created_at)"'
+
+  **Step 2 — Classify each PR**
+  - author = dependabot[bot] → dep PR
+  - author = github-actions[bot] → bot PR (skip unless release PR)
+  - otherwise → human PR
+
+  **Step 3 — Act**
+  For dep PRs: check CI with `gh pr checks <num> --repo <repo>`.
+  - All passing → merge: `gh pr merge <num> --repo <repo> --squash`
+  - Failing → skip and note
+  - Dirty (will regenerate) → close: `gh pr close <num> --repo <repo>`
+
+  For human PRs: read diff summary, check CI, check conflicts.
+  - Report status only. Never merge or close.
+
+  **Step 4 — Write report**
+  Write to loops/oss-pr-monitor/report.md with a table:
+  | # | Repo | Title | Author | Type | CI | Action | Pending Reason |
+
+  **Step 5 — Update STATE.md**
+  Set last_run_status, last_run, clear last_processed_repo on success.

agent_toolkit_cli-1.0.3.data/data/agent_toolkit/data/loops/oss-triage/loop.yaml

@@ -0,0 +1,67 @@
+# Loop starter: oss-triage
+# An L1 loop that triages issues across a multi-repo OSS ecosystem.
+# Cadence: daily. Cost: medium. Tier: L1 (report-only + label/comment).
+# Designed for maintainers managing 20-50 repos.
+
+name: oss-triage
+description: "Triage issues across OSS ecosystem repos (L1, daily)"
+tier: L1
+cadence: 1d
+resumable: true
+
+goal: |
+  Scan open issues across all configured repos for items needing attention.
+  Apply labels and respond to questions where obvious. Report everything else.
+
+allowlist:
+  - label
+  - comment
+  - assign
+deny:
+  - merge
+  - close
+  - push
+  - approve
+  - force-push
+
+exit_conditions:
+  - goal_met
+  - budget_exhausted
+  - human_escalation
+
+budget:
+  max_tokens: 150000
+  max_runs_per_day: 1
+  max_wall_seconds: 1200
+
+verifier: null
+
+request: |
+  You are running the OSS Issue Triage loop.
+
+  **Resumability (read first):**
+  Read loops/oss-triage/STATE.md. If `last_processed_repo` is set, skip all
+  repos before that name. After each repo, update STATE.md:
+    last_processed_repo: <owner>/<repo>
+  On successful completion, clear last_processed_repo and set last_run_status: success.
+
+  **Style rules:**
+  - Never @mention anyone. Never leave AI-looking comments.
+  - If action is obvious (label, response) → do it silently.
+  - If unsure → skip and note in report.
+
+  **Step 1 — Find issues needing attention**
+  For each repo, find issues where the most recent comment is NOT from the maintainer:
+    gh api "repos/$repo/issues?state=open&per_page=50" --jq '...'
+
+  **Step 2 — Classify and act**
+  - Question with no response → draft a response, post as comment
+  - Issue with no label → apply appropriate label (bug, enhancement, documentation, etc.)
+  - Bug with no reproducer → comment asking for minimal reproduction
+  - Security report → escalate (human_escalation)
+
+  **Step 3 — Write report**
+  Write to loops/oss-triage/report.md with sections:
+  - Actions taken (labels applied, comments posted)
+  - Pending items (issues that need human review)
+  - Escalations (if any)

agent_toolkit_cli-1.0.3.data/data/agent_toolkit/data/loops/post-merge-cleanup/loop.yaml

@@ -0,0 +1,44 @@
+# Loop starter: post-merge-cleanup
+# An L2 loop that runs off-peak housekeeping after merges.
+# Cadence: 6 hours. Cost: low. Tier: L2 (limited write access).
+
+name: post-merge-cleanup
+description: "Off-peak housekeeping after merges (L2, low impact)"
+tier: L2
+cadence: 6h
+
+goal: |
+  Delete merged branches, close stale issues, and compact the project board.
+  Only operate on branches/issues that are clearly finished.
+  Never delete branches with open PRs.
+
+allowlist:
+  - delete_merged_branch
+  - close_stale_issue
+  - comment
+deny:
+  - merge
+  - approve
+  - delete-unmerged-branch
+  - close-active-issue
+
+exit_conditions:
+  - goal_met
+  - budget_exhausted
+  - human_escalation
+
+budget:
+  max_tokens: 20000
+  max_runs_per_day: 4
+  max_wall_seconds: 300
+
+verifier: null
+
+request: |
+  You are the post-merge cleanup loop for this repository.
+  1. List branches merged into main (git branch -r --merged main).
+  2. Delete branches that have been merged > 7 days ago (skip: main, develop, release/*).
+  3. List issues closed by merged PRs but not yet closed — close them.
+  4. List issues with no activity > 90 days — post a "stale?" comment (do NOT close).
+  5. Write plan.md: branches deleted, issues closed, stale comments posted.
+  6. If uncertain about any action: skip it and note it in plan.md.

agent_toolkit_cli-1.0.3.data/data/agent_toolkit/data/loops/pr-babysitter/loop.yaml

@@ -0,0 +1,46 @@
+# Loop starter: pr-babysitter
+# An L2 loop that watches open PRs and posts review comments every 15 minutes.
+# Cadence: 15 minutes. Cost: high. Tier: L2 (PR-gated).
+#
+# Usage:
+#   ./bin/loop init pr-babysitter --repo owner/repo
+
+name: pr-babysitter
+description: "Monitor open PRs and post review comments (L2, PR-gated)"
+tier: L2
+cadence: 15m
+
+goal: |
+  Review any open PRs that have not received a review in the last hour.
+  Post constructive review comments. Do NOT approve or merge.
+
+allowlist:
+  - comment
+deny:
+  - merge
+  - approve
+  - close
+  - push
+  - label
+
+exit_conditions:
+  - goal_met
+  - budget_exhausted
+  - human_escalation
+
+budget:
+  max_tokens: 80000
+  max_runs_per_day: 96
+  max_wall_seconds: 600
+
+verifier: agent-toolkit-code-reviewer
+
+request: |
+  You are the PR babysitter for this repository.
+  1. List all open PRs (gh pr list).
+  2. For each PR that has no review in the last 60 minutes:
+     a. Read the diff (gh pr diff).
+     b. Post a review comment with: summary, 1-3 specific suggestions, any blockers.
+  3. Do NOT approve or request changes — leave as a comment only.
+  4. If a PR has a security issue: escalate (human_escalation exit).
+  5. Write plan.md listing which PRs you reviewed and the comments posted.

agent_toolkit_cli-1.0.3.data/data/agent_toolkit/data/mcp/templates/clickup/README.md

@@ -0,0 +1,45 @@
+# ClickUp MCP Template
+
+> **Deprecated** — The ClickUp MCP server is no longer the recommended integration.
+> Use the [`clickup` CLI](https://triptechtravel.github.io/clickup-cli/) instead.
+> The workstation installs the global skill at `~/.local/share/agent-toolkit/skills/clickup-cli/SKILL.md`.
+
+## Why the CLI is preferred
+
+| | ClickUp MCP | `clickup` CLI |
+|---|---|---|
+| Token cost | High — MCP responses are verbose JSON blobs | Low — structured `--json`/`--jq` output, ~90% less noise with `rtk` |
+| Auth | Requires server process + API token in config | Token stored in system keyring; CI via `--with-token` |
+| Git integration | None | Auto-detects task IDs from branch names |
+| Maintenance | External server process to keep running | Single binary, no daemon |
+
+## Migration
+
+Remove the ClickUp MCP server from your agent config and install the CLI instead:
+
+```bash
+# Install (macOS/Linux with Homebrew)
+brew install triptechtravel/tap/clickup
+
+# Install (go)
+go install github.com/triptechtravel/clickup-cli/cmd/clickup@latest
+
+# Authenticate
+clickup auth login
+
+# Select default space
+clickup space select
+```
+
+The `clickup-cli` skill is deployed by chezmoi at `~/.local/share/agent-toolkit/skills/clickup-cli/` and linked globally for Claude Code, Cursor, Copilot, OpenCode, and pi.
+
+## Legacy reference
+
+The MCP config template and wrapper script are kept below for reference only.
+Do not use them for new setups.
+
+### Required environment variables (legacy)
+
+- `CLICKUP_API_TOKEN`
+
+Use `config.template.json` and `wrapper.sh` as legacy examples only.

agent_toolkit_cli-1.0.3.data/data/agent_toolkit/data/mcp/templates/clickup/config.template.json

@@ -0,0 +1,7 @@
+{
+  "name": "clickup",
+  "command": "mcp-clickup-server",
+  "env": {
+    "CLICKUP_API_TOKEN": "${CLICKUP_API_TOKEN}"
+  }
+}

agent_toolkit_cli-1.0.3.data/data/agent_toolkit/data/mcp/templates/clickup/wrapper.sh

@@ -0,0 +1,23 @@
+#!/usr/bin/env bash
+set -eo pipefail
+
+if [[ -t 1 && -z ${NO_COLOR:-} ]]; then
+  c_reset=$'\033[0m'
+  c_blue=$'\033[1;34m'
+  c_red=$'\033[1;31m'
+else
+  c_reset=''
+  c_blue=''
+  c_red=''
+fi
+
+info() { printf '%b[mcp-wrapper]%b %s\n' "$c_blue" "$c_reset" "$*"; }
+fail() { printf '%b[mcp-wrapper]%b %s\n' "$c_red" "$c_reset" "$*"; }
+
+if [[ -z ${CLICKUP_API_TOKEN:-} ]]; then
+  fail "CLICKUP_API_TOKEN is required" >&2
+  exit 1
+fi
+
+info "starting mcp-clickup-server"
+exec mcp-clickup-server

agent_toolkit_cli-1.0.3.data/data/agent_toolkit/data/mcp/templates/figma/README.md

@@ -0,0 +1,56 @@
+# Figma MCP Template
+
+Connects an AI tool to the remote Figma MCP server
+(`https://mcp.figma.com/mcp`, streamable HTTP with bearer-token auth).
+
+## Required environment variables
+
+- `FIGMA_OAUTH_TOKEN` — personal access token or OAuth token with read +
+  assets scopes.
+- `FIGMA_REGION` — Figma region header (default `us-east-1`).
+
+Store them in `~/.config/agent-toolkit/env.d/figma.env` (covered by `dots-loadenv`):
+
+```bash
+mkdir -p ~/.config/agent-toolkit/env.d
+cat >> ~/.config/agent-toolkit/env.d/figma.env <<'EOF'
+export FIGMA_OAUTH_TOKEN="<paste-token-here>"
+export FIGMA_REGION="us-east-1"
+EOF
+chmod 600 ~/.config/agent-toolkit/env.d/figma.env
+```
+
+`dots-doctor` will pick up `figma.env` under "Integrations" without printing
+the value.
+
+> [!CAUTION]
+> Tokens copied from the Figma UI must not include surrounding quotes. Never
+> commit `figma.env` to a repository.
+
+## How to use
+
+The transport is **streamable HTTP** — there is no local `command`/`wrapper.sh`.
+Each AI tool registers MCP servers in its own configuration file:
+
+| AI tool | Configuration file |
+|---------|--------------------|
+| Claude Code | `~/.claude/mcp.json` (or `claude mcp add figma --transport http --url https://mcp.figma.com/mcp --header "Authorization: Bearer $FIGMA_OAUTH_TOKEN" --header "X-Figma-Region: $FIGMA_REGION"`) |
+| Cursor | `~/.cursor/mcp.json` |
+| OpenCode | `~/.config/opencode/mcp.json` |
+| Windsurf | `~/.codeium/windsurf/mcp_config.json` |
+
+Copy the values from `config.template.json` and substitute the env vars at
+registration time. Restart your AI tool so it re-reads the MCP config.
+
+## Verify
+
+1. Run `dots-doctor` and confirm `figma.env` is listed under Integrations.
+2. Restart your AI tool.
+3. Ask the AI to call `whoami` on the Figma MCP — it should return your Figma
+   user identity.
+
+## See also
+
+- `~/.local/share/agent-toolkit/skills/figma/SKILL.md` and the `figma-*` skill
+  family.
+- `docs/MCP_TEMPLATES.md`

agent_toolkit_cli-1.0.3.data/data/agent_toolkit/data/mcp/templates/figma/config.template.json

@@ -0,0 +1,9 @@
+{
+  "name": "figma",
+  "transport": "streamable_http",
+  "url": "https://mcp.figma.com/mcp",
+  "headers": {
+    "Authorization": "Bearer ${FIGMA_OAUTH_TOKEN}",
+    "X-Figma-Region": "${FIGMA_REGION}"
+  }
+}

agent_toolkit_cli-1.0.3.data/data/agent_toolkit/data/mcp/templates/github/README.md

@@ -0,0 +1,11 @@
+# GitHub MCP Template
+
+## Required environment variables
+
+- `GITHUB_TOKEN`
+
+## Usage
+
+1. Copy `config.template.json` to your MCP client config.
+2. Export `GITHUB_TOKEN`.
+3. Run `./wrapper.sh` as an example launcher.

agent_toolkit_cli-1.0.3.data/data/agent_toolkit/data/mcp/templates/github/config.template.json

@@ -0,0 +1,7 @@
+{
+  "name": "github",
+  "command": "mcp-github-server",
+  "env": {
+    "GITHUB_TOKEN": "${GITHUB_TOKEN}"
+  }
+}

agent_toolkit_cli-1.0.3.data/data/agent_toolkit/data/mcp/templates/github/wrapper.sh

@@ -0,0 +1,23 @@
+#!/usr/bin/env bash
+set -eo pipefail
+
+if [[ -t 1 && -z ${NO_COLOR:-} ]]; then
+  c_reset=$'\033[0m'
+  c_blue=$'\033[1;34m'
+  c_red=$'\033[1;31m'
+else
+  c_reset=''
+  c_blue=''
+  c_red=''
+fi
+
+info() { printf '%b[mcp-wrapper]%b %s\n' "$c_blue" "$c_reset" "$*"; }
+fail() { printf '%b[mcp-wrapper]%b %s\n' "$c_red" "$c_reset" "$*"; }
+
+if [[ -z ${GITHUB_TOKEN:-} ]]; then
+  fail "GITHUB_TOKEN is required" >&2
+  exit 1
+fi
+
+info "starting mcp-github-server"
+exec mcp-github-server

agent_toolkit_cli-1.0.3.data/data/agent_toolkit/data/mcp/templates/linear/README.md

@@ -0,0 +1,49 @@
+# Linear MCP Template
+
+Connects an AI tool to Linear via the official remote MCP server
+(`https://mcp.linear.app/mcp`, OAuth — no API token needed).
+
+## Required environment variables
+
+- None. Authentication is OAuth, prompted by your AI tool on first call.
+
+## How to use
+
+The transport is **streamable HTTP**, not a local `command`/`wrapper.sh`. Each
+AI tool registers MCP servers slightly differently — pick the relevant
+configuration file and copy the URL from `config.template.json`:
+
+| AI tool | Configuration file |
+|---------|--------------------|
+| Claude Code | `~/.claude/mcp.json` (or `claude mcp add linear --transport http --url https://mcp.linear.app/mcp`) |
+| Cursor | `~/.cursor/mcp.json` |
+| OpenCode | `~/.config/opencode/mcp.json` |
+| Windsurf | `~/.codeium/windsurf/mcp_config.json` |
+
+The first Linear tool call triggers an OAuth window in your browser. After login
+the session is cached by the AI tool.
+
+## Windows / WSL fallback
+
+If direct streamable-HTTP connections are blocked on Windows, run the MCP
+through WSL using `mcp-remote`:
+
+```jsonc
+{
+  "mcpServers": {
+    "linear": {
+      "command": "wsl",
+      "args": ["npx", "-y", "mcp-remote", "https://mcp.linear.app/sse", "--transport", "sse-only"]
+    }
+  }
+}
+```
+
+That snippet is also embedded in `config.template.json` under the
+`_comment_windows_wsl_fallback` key for reference.
+
+## See also
+
+- `~/.local/share/agent-toolkit/skills/linear/SKILL.md` — the linear skill that
+  drives this MCP.
+- `docs/MCP_TEMPLATES.md`

agent_toolkit_cli-1.0.3.data/data/agent_toolkit/data/mcp/templates/linear/config.template.json

@@ -0,0 +1,10 @@
+{
+  "name": "linear",
+  "transport": "streamable_http",
+  "url": "https://mcp.linear.app/mcp",
+  "auth": "oauth",
+  "_comment_windows_wsl_fallback": {
+    "command": "wsl",
+    "args": ["npx", "-y", "mcp-remote", "https://mcp.linear.app/sse", "--transport", "sse-only"]
+  }
+}

agent_toolkit_cli-1.0.3.data/data/agent_toolkit/data/mcp/templates/notion/README.md

@@ -0,0 +1,7 @@
+# Notion MCP Template
+
+## Required environment variables
+
+- `NOTION_API_TOKEN`
+
+Use `config.template.json` and `wrapper.sh` as baseline examples.

agent_toolkit_cli-1.0.3.data/data/agent_toolkit/data/mcp/templates/notion/config.template.json

@@ -0,0 +1,7 @@
+{
+  "name": "notion",
+  "command": "mcp-notion-server",
+  "env": {
+    "NOTION_API_TOKEN": "${NOTION_API_TOKEN}"
+  }
+}

agent_toolkit_cli-1.0.3.data/data/agent_toolkit/data/mcp/templates/notion/wrapper.sh

@@ -0,0 +1,23 @@
+#!/usr/bin/env bash
+set -eo pipefail
+
+if [[ -t 1 && -z ${NO_COLOR:-} ]]; then
+  c_reset=$'\033[0m'
+  c_blue=$'\033[1;34m'
+  c_red=$'\033[1;31m'
+else
+  c_reset=''
+  c_blue=''
+  c_red=''
+fi
+
+info() { printf '%b[mcp-wrapper]%b %s\n' "$c_blue" "$c_reset" "$*"; }
+fail() { printf '%b[mcp-wrapper]%b %s\n' "$c_red" "$c_reset" "$*"; }
+
+if [[ -z ${NOTION_API_TOKEN:-} ]]; then
+  fail "NOTION_API_TOKEN is required" >&2
+  exit 1
+fi
+
+info "starting mcp-notion-server"
+exec mcp-notion-server

agent_toolkit_cli-1.0.3.data/data/agent_toolkit/data/mcp/templates/slack/README.md

@@ -0,0 +1,8 @@
+# Slack MCP Template
+
+## Required environment variables
+
+- `SLACK_BOT_TOKEN`
+- `SLACK_APP_TOKEN`
+
+Use `config.template.json` and `wrapper.sh` as baseline examples.

agent_toolkit_cli-1.0.3.data/data/agent_toolkit/data/mcp/templates/slack/config.template.json

@@ -0,0 +1,8 @@
+{
+  "name": "slack",
+  "command": "mcp-slack-server",
+  "env": {
+    "SLACK_BOT_TOKEN": "${SLACK_BOT_TOKEN}",
+    "SLACK_APP_TOKEN": "${SLACK_APP_TOKEN}"
+  }
+}

agent_toolkit_cli-1.0.3.data/data/agent_toolkit/data/mcp/templates/slack/wrapper.sh

@@ -0,0 +1,23 @@
+#!/usr/bin/env bash
+set -eo pipefail
+
+if [[ -t 1 && -z ${NO_COLOR:-} ]]; then
+  c_reset=$'\033[0m'
+  c_blue=$'\033[1;34m'
+  c_red=$'\033[1;31m'
+else
+  c_reset=''
+  c_blue=''
+  c_red=''
+fi
+
+info() { printf '%b[mcp-wrapper]%b %s\n' "$c_blue" "$c_reset" "$*"; }
+fail() { printf '%b[mcp-wrapper]%b %s\n' "$c_red" "$c_reset" "$*"; }
+
+if [[ -z ${SLACK_BOT_TOKEN:-} || -z ${SLACK_APP_TOKEN:-} ]]; then
+  fail "SLACK_BOT_TOKEN and SLACK_APP_TOKEN are required" >&2
+  exit 1
+fi
+
+info "starting mcp-slack-server"
+exec mcp-slack-server

agent_toolkit_cli-1.0.3.data/data/agent_toolkit/data/profiles/claude-code/CLAUDE.md

@@ -0,0 +1,66 @@
+# AI Toolkit Dev Companion — Global Instructions
+
+You are the AI Toolkit Dev Companion. Ensure all work follows agent-toolkit standards and conventions.
+
+## Repository inspection order
+
+When starting work in any repository, read in this order:
+
+1. `README.md` — understand the project purpose and stack
+2. `docs/` directory — architecture, design, and operational docs
+3. `AGENTS.md` or `.claude/CLAUDE.md` — agent-specific instructions (primary contract)
+4. `CONTRIBUTING.md` — contribution guidelines
+5. PR templates (`.github/PULL_REQUEST_TEMPLATE.md`)
+6. Task runners: `Makefile`, `package.json` scripts, `justfile`
+7. `devcontainer.json` and CI workflows (`.github/workflows/`)
+8. Configuration files
+
+Always cite which file a rule or convention comes from.
+
+## agent-toolkit standards
+
+- Shell scripts: `set -euo pipefail`, idempotent, OS detection before package manager calls
+- chezmoi repos: `.chezmoiroot` points to `home/`, `` prefix for internal commands
+- Documentation: update when behavior changes
+- Secrets: never commit — use `.env.example` for templates
+- English: all documentation, commit messages, and ticket descriptions
+
+## CLI tool names to know
+
+- **Confluence CLI**: `confluence-as` (also available as `confluence` via wrapper). The external skill pack docs reference `confluence` — both work.
+- **JIRA CLI**: `jira-as`
+- All other agent-toolkit helpers use `` prefix: `doctor`, `skills`, `update-check`
+
+## Agent delegation
+
+Available subagents (invoke with `@name` in your message):
+- `@planner` — feature planning and task breakdown
+- `@code-reviewer` — code quality review
+- `@security-reviewer` — security audit
+- `@tdd-guide` — TDD workflow
+- `@reference-lookup` — agent-toolkit examples from public examples
+- `@architect` — system design and architecture decisions
+- `@build-error-resolver` — build/CI error diagnosis
+- `@database-reviewer` — SQL and database review
+- `@performance-optimizer` — performance analysis
+- `@typescript-reviewer` — TypeScript/JS code review
+- `@e2e-runner` — Playwright E2E tests
+- `@refactor-cleaner` — dead code cleanup and refactoring
+- `@tech-assistant` — agent-toolkit operational procedures
+
+These are agents defined in `~/.claude/agents/` — they are NOT skills.
+
+## When working on client projects
+
+- Respect existing patterns and conventions in the project
+- Check for project-specific AGENTS.md or CLAUDE.md
+- Follow the project's established branching and PR strategy
+- Escalate conflicts between agent-toolkit standards and project conventions
+
+## Output
+
+Cite sources (which file the convention came from). Surface conflicts explicitly. Ask when instructions are ambiguous rather than assuming.
+
+---
+
+@RTK.md