app-chat-request

app-chat-request is a skill for Claude Code, Codex from juliakrivchikova/AccordAgents-desktop-app. It costs 65 tokens per session (828 once invoked), scanned A, original, Apache-2.0.

A skill for asking another member of an AccordAgents chat to provide a specific answer or complete a bounded task.

In plain words
What is it for?
It helps send targeted questions or tasks to a named chat participant and attach the participant’s response to the conversation.
Why use it?
It prevents requests from being mistaken for ordinary mentions and manages the handoff and reply.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps send targeted questions or tasks to a named chat participant and attach the participant’s response to the conversation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/juliakrivchikova/accordagents-desktop-app/app-chat-request
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 juliakrivchikova/AccordAgents-desktop-app --skill app-chat-request
Clone the repo
git clone --depth 1 https://github.com/juliakrivchikova/AccordAgents-desktop-app

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.

agentmods badge for app-chat-request

README.md
[![agentmods](https://agentmods.dev/badge/skills/juliakrivchikova/accordagents-desktop-app/app-chat-request/github.svg)](https://agentmods.dev/skills/juliakrivchikova/accordagents-desktop-app/app-chat-request)
Your own site
<a href="https://agentmods.dev/skills/juliakrivchikova/accordagents-desktop-app/app-chat-request"><img src="https://agentmods.dev/badge/skills/juliakrivchikova/accordagents-desktop-app/app-chat-request/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.

agentmods 80×15 button for app-chat-request

Your own site · 80×15
<a href="https://agentmods.dev/skills/juliakrivchikova/accordagents-desktop-app/app-chat-request"><img src="https://agentmods.dev/badge/skills/juliakrivchikova/accordagents-desktop-app/app-chat-request.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 828 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 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.1 $0.00065 $0.00828
Opus 5 $0.00032 $0.00414
Sonnet 5 $0.00013 $0.00166
Haiku 4.5 $0.00006 $0.00083

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

Security

Grade A, and why

app-chat-request 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 12d 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.

src/main/appSkills/app-chat-request/SKILL.md · 93 lines

How it starts

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

Request another chat participant

Use this skill when another current chat participant should answer a concrete question or task.

A normal @handle mention is only prose. It is appropriate for attribution, discussion, or referring to what someone said. When the target participant is expected to answer, use app_chat_request_participants so the app can validate policy, ask User for approval when needed, run the target, attach the reply, and resume your turn.

Do not use this skill when User is only asking you to answer directly, when a participant is mentioned only for attribution, or when the other participant is not expected to respond.

Prepare the request

  1. Identify the target participant handle and the exact prompt they should answer.
  2. If the target handle is explicit in the current turn, use it directly. Do not call discovery just to confirm an obvious handle.
  3. If the target is ambiguous, missing, or described by role instead of handle, call app_chat_get_participants once and choose the matching current participant. If no single target is clear, ask User to clarify in a normal chat message and end your turn.
  4. Keep the prompt concrete and self-contained. Include only the context the target needs to answer. Do not ask the target to decide User-owned goals, preferences, or acceptance criteria.
  5. Include a short reason when it helps User understand why approval is being requested.
  6. When asking another participant to review a plan, prefer scrutiny-first wording such as: "Review this plan for blockers, incorrect assumptions, missing edge cases, or simpler alternatives. If none, reply with only No objections." Avoid "confirm or add" unless confirmation is truly the only task. The app also rewrites confirm/agree-style prompts before they reach the target, but starting with scrutiny-first wording yourself reduces bias more reliably.

Call the tool

Call app_chat_request_participants:

{
  "requests": [
    {
      "target": "target-handle",
      "prompt": "Concrete question or task for the target participant.",
      "reason": "Optional brief reason this participant input is needed."
    }
  ],
  "timeoutMs": 120000,
  "resumeRequester": true
}

Read the full file on GitHub · 93 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.

  1. 12d ago First seen · 93 lines · 65 tokens per session scan A c7c71939a6bd

Subscribe to this mod's changes

app-chat-request is a skill published in the GitHub repository juliakrivchikova/AccordAgents-desktop-app (5 stars, last pushed 3d ago), licensed Apache-2.0. It adds 65 tokens to every session and 828 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens