Skip to content
Back to skills

Coagent8 Consult

ASecurity

Ask another local coding agent (Codex, Claude Code or Antigravity) for a second opinion through the CoAgent8 consult tool. Use when the user wants a second opinion, a check of a design or plan, help with a stubborn bug, or names CoAgent8 consult. Not for reading files, running commands or questions the workspace already answers.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 19, 2026
ai-agentsgobackend

Works with

  • claude code

Security analysis

A100/100

Scanned October 19, 2026

npx -y skills add oktawianwybieralski/coagent8 --skill coagent8-consult --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Coagent8 Consult?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Coagent8 Consult
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/oktawianwybieralski-coagent8-consult/badge)](https://www.skillsdirectory.com/skills/oktawianwybieralski-coagent8-consult)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: coagent8-consult
description: Ask another local coding agent (Codex, Claude Code or Antigravity) for a second opinion through the CoAgent8 consult tool. Use when the user wants a second opinion, a check of a design or plan, help with a stubborn bug, or names CoAgent8 consult. Not for reading files, running commands or questions the workspace already answers.
---

# CoAgent8 consult

Text the user typed with this command is the question; otherwise take it from
the conversation.

1. Write a self-contained `proposal`: the question, the design, constraints and
   what was already tried. The other agent has not seen this conversation.
   Name files and symbols instead of pasting their content: arguments travel as
   escaped JSON, and the other agent reads the workspace itself. "Is the retry
   loop in `src/a.ts` (`writeWithRetry`) safe with concurrent writers?" is good;
   "thoughts?" is not.
2. Put workspace paths the other agent should read itself in `context_files`;
   only the paths are sent. Paste only what is not in the workspace, such as an
   error message or a short excerpt of a log. Set `task_type` to `architecture`, `debug` or
   `implementation` when you want that kind of analysis; omit it for a plain
   question. Put required criteria in `specific_questions`.
3. Leave `backend`, `model` and `reasoning_effort` unset unless the user named
   one. For a user's price limit or range (e.g. "X-Y" means `output_price_below: Y`),
   pass `output_price_below` (USD per million output tokens, strict) and leave
   `model` unset; the server picks the qualifying default or the most recently
   released qualifying model. `coagent8-doctor` lists models, prices and the day
   the price list added each model.
4. For a follow-up on the same topic pass the `session_handle` from the result
   footer. A call without it starts a fresh agent that rereads everything.
5. Before calling a model that `coagent8-doctor` tags `ask` (expensive,
   unpriced or on the user's ask list), tell the user its price and that the
   server will show an approval form, and let them choose it or a cheaper model.
   Never call a model tagged `deny`: the user denied it. Their answer in chat is
   not approval: only the form is. Never approve on the user's behalf, never
   change approval settings and never switch models silently to avoid the
   question. If the form closes without an answer, relay the refusal's ways out
   to the user. On a price-limit refusal, report the reason.

The answer is another model's opinion. Verify its claims against the code
before acting, and tell the user where you disagree and why. The consulted agent
runs read-only: it cannot edit files or run commands for you.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.