ask

A command for sending a question to another teammate's coding agent and waiting for its reply. It can try once more if the first wait times out.

In plain words
What is it for?
Use it to ask a named teammate's agent a project question and receive the answer, or confirm that the question is still awaiting a response.
Why use it?
It avoids manually finding the teammate or repeatedly checking for an answer. If no reply arrives, the question remains delivered and can be answered later.

Command

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.

agentmods
npx agentmods add commands/joaquinbejar/ai-crew-sync/ask
Clone the repo
git clone --depth 1 https://github.com/joaquinbejar/ai-crew-sync
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 218 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.

ModelPer sessionOnce invoked
Fable 5 $0.00012 $0.00218
Opus 5 $0.00006 $0.00109
Sonnet 5 $0.00002 $0.00044
Haiku 4.5 $0.00001 $0.00022

Measured 2d ago against content hash f908f28f36ac, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ask 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 2d 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.

plugin/commands/ask.md · 15 lines

What it actually says

Ask a teammate's agent a question over the crew bus and wait for the answer.

Input: $ARGUMENTS

Steps:

  1. The first word of the input is the teammate's handle; the rest is the question. If the handle looks wrong (empty question, or list_agents does not know it), ask me to rephrase instead of guessing.
  2. Call ask_agent with to set to the handle and question set to the question, worded as I gave it. Use the default timeout.
  3. If it returns answered: true, show me the answer verbatim, attributed to the teammate.
  4. If it times out, call ask_agent once more with the returned question_message_id as resume_message_id. If that also times out, tell me the question was delivered but unanswered, and that the reply will show up in my inbox — do not keep blocking.
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.

  1. 2d ago First seen · 15 lines · 12 tokens per session scan A f908f28f36ac

Subscribe to this mod's changes

ask is a command published in the GitHub repository joaquinbejar/ai-crew-sync (4 stars, last pushed 20d ago), licensed MIT. It adds 12 tokens to every session and 218 once invoked, about $0.0001 per session on Opus 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-31.