What is client-compatibility?

A platform-detection skill for coordinating helper agents across command-line tools, Visual Studio Code, JetBrains, and GitHub.com.

Use it to choose the appropriate agent-spawning method and adjust coordination behavior to the environment where the task is running.

Different coding environments provide different tools for starting and collecting work from helper agents.

client-compatibility — Skill for Claude Code and Codex by DanWahlin

Install

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.

Any agent

npx skills add DanWahlin/ai-agent-board --skill client-compatibility

Clone the repo

git clone --depth 1 https://github.com/DanWahlin/ai-agent-board

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/danwahlin/ai-agent-board/client-compatibility.svg)](https://agentmods.dev/skills/danwahlin/ai-agent-board/client-compatibility)

Your own site

<a href="https://agentmods.dev/skills/danwahlin/ai-agent-board/client-compatibility"><img src="https://agentmods.dev/badge/skills/danwahlin/ai-agent-board/client-compatibility.svg" alt="Measured on agentmods" height="20"></a>

Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,238 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

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.00018	$0.01238
Opus 5	$0.00009	$0.00619
Sonnet 5	$0.00004	$0.00248
Haiku 4.5	$0.00002	$0.00124

Measured 8d ago against content hash d8da5e1e9918, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

client-compatibility 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.

Origin

This is a copy

100% identical to client-compatibility — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.squad/templates/skills/client-compatibility/SKILL.md · 90 lines

How it starts

The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Context

Squad runs on multiple Copilot surfaces (CLI, VS Code, JetBrains, GitHub.com). The coordinator must detect its platform and adapt spawning behavior accordingly. Different tools are available on different platforms, requiring conditional logic for agent spawning, SQL usage, and response timing.

Patterns

Platform Detection

Before spawning agents, determine the platform by checking available tools:

CLI mode — task tool is available → full spawning control. Use task with agent_type, mode, model, description, prompt parameters. Collect results via read_agent.
VS Code mode — runSubagent or agent tool is available → conditional behavior. Use runSubagent with the task prompt. Drop agent_type, mode, and model parameters. Multiple subagents in one turn run concurrently (equivalent to background mode). Results return automatically — no read_agent needed.
Fallback mode — neither task nor runSubagent/agent available → work inline. Do not apologize or explain the limitation. Execute the task directly.

If both task and runSubagent are available, prefer task (richer parameter surface).

VS Code Spawn Adaptations

When in VS Code mode, the coordinator changes behavior in these ways:

Spawning tool: Use runSubagent instead of task. The prompt is the only required parameter — pass the full agent prompt (charter, identity, task, hygiene, response order) exactly as you would on CLI.
Parallelism: Spawn ALL concurrent agents in a SINGLE turn. They run in parallel automatically. This replaces mode: "background" + read_agent polling.
Model selection: Accept the session model. Do NOT attempt per-spawn model selection or fallback chains — they only work on CLI. In Phase 1, all subagents use whatever model the user selected in VS Code's model picker.
Scribe: Cannot fire-and-forget. Batch Scribe as the LAST subagent in any parallel group. Scribe is light work (file ops only), so the blocking is tolerable.
Launch table: Skip it. Results arrive with the response, not separately. By the time the coordinator speaks, the work is already done.
read_agent: Skip entirely. Results return automatically when subagents complete.
agent_type: Drop it. All VS Code subagents have full tool access by default. Subagents inherit the parent's tools.
description: Drop it. The agent name is already in the prompt.
Prompt content: Keep ALL prompt structure — charter, identity, task, hygiene, response order blocks are surface-independent.

Read the full file on GitHub · 90 lines

Changes

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 · 90 lines · 18 tokens per session scan A d8da5e1e9918

Subscribe to this mod's changes

client-compatibility is a skill published in the GitHub repository DanWahlin/ai-agent-board (57 stars, last pushed 13d ago), licensed MIT. It adds 18 tokens to every session and 1,238 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to client-compatibility, differing in 0 lines, and is treated as a copy.

Building agents Claude Code agents ai codex github-copilot-cli kanban-board

foundry-config-setup

Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.

microsoft/agent-framework · 65 tokens

deploy-docker-compose

Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…

omnigent-ai/omnigent · 84 tokens

client-compatibility