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.
npx agentmods add skills/cogni-work/insight-wave/consult-setupnpx skills add cogni-work/insight-wave --skill consult-setupgit clone --depth 1 https://github.com/cogni-work/insight-waveWrote 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.
[](https://agentmods.dev/skills/cogni-work/insight-wave/consult-setup)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/consult-setup"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/consult-setup.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00139 | $0.02093 |
| Opus 5 | $0.00069 | $0.01046 |
| Sonnet 5 | $0.00028 | $0.00419 |
| Haiku 4.5 | $0.00014 | $0.00209 |
Grade A, and why
consult-setup 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engagement Setup
Initialize a cogni-consult engagement: frame the desired outcome with the consultant, scaffold the action-fields-WBS directory structure, bind the one cogni-knowledge base the whole engagement compounds research into, and register the engagement for cross-session discovery. This is the entry point — without it, no later skill has a project to write to.
Setup deliberately stays light: it captures the outcome and the research spine, nothing more. The SMART key question, the five scoping dimensions, and the 3-6 action fields are consult-scope's job; the two default advisor personas (consulting-partner, project-manager) now ship at scaffold so personas/ is never empty, while engagement-specific scope-seeded stakeholder personas still come from consult-personas; deliverables emerge inside action fields. If an engagement already exists for this client/topic, do not create a duplicate — dispatch Skill("cogni-consult:consult-resume") to re-enter it.
Workflow
0. Resolve the Interaction Language
Before any user-facing output, resolve the interaction language — the
workspace default, overridden by the user's message language — per
$CLAUDE_PLUGIN_ROOT/references/interaction-language.md, which owns the
resolution ladder. Conduct the entire conversation in the resolved language.
It is independent of the engagement's language field, which is the
deliverable axis. This contract holds on the default path: it does not depend
on an output style being active.
The description of a Bash tool call is rendered to the consultant, so it is
user copy — write it in the interaction language, outcome-shaped, at most 6
words, with no script, file, or skill names, and never derived from the
script's filename or header comment. Worked pair:
Discover cogni-consult engagements → Laufende Engagements holen.
Section (f) of the canonical ecosystem register owns these five constraints —
edit them there first, then mirror into
$CLAUDE_PLUGIN_ROOT/references/user-facing-output.md and here.
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.
- today Changed · +5 lines 845dee990cb3
- 5d ago First seen · 126 lines · 139 tokens per session scan A 16821cfda42a
consult-setup is a skill published in the GitHub repository cogni-work/insight-wave (12 stars, last pushed yesterday), licensed Apache-2.0. It adds 139 tokens to every session and 2,093 once invoked, about $0.0007 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-30.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
cog-knowledge-consolidation
Build structured knowledge frameworks from scattered vault notes with source attribution.