Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add cogni-work/insight-wave/plugin install cogni-consultWrote 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-action-fields)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/consult-action-fields"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/consult-action-fields.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.1 | $0.00238 | $0.04872 |
| Opus 5 | $0.00119 | $0.02436 |
| Sonnet 5 | $0.00048 | $0.00974 |
| Haiku 4.5 | $0.00024 | $0.00487 |
Grade A, and why
consult-action-fields 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.
How it starts
The opening of the file, as written. The whole thing — 401 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Action-Field WBS Management
Manage the engagement's work-breakdown structure: each action field named
during scoping is a container whose field.json manifests the deliverables
that complete it. This skill renders the WBS dashboard (fields × deliverables
× status), plans each field's deliverable set from
$CLAUDE_PLUGIN_ROOT/references/deliverable-types.md, recommends the next
unstarted deliverable, and keeps consult-project.json and the
action-fields/ tree consistent when fields are added, split, or merged.
It manages the manifest layer only — producing a deliverable is the work of
its producing route (a consult-design-thinking run by default).
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.
The register that output follows has two tiers. The overlay
$CLAUDE_PLUGIN_ROOT/references/user-facing-output.md carries this plugin's own
state lexicon, coinages and German step vocabulary, and opens with the command
that reads the canonical ecosystem register behind it — which owns scope, the
table contract, step announcements and brevity budgets, and the executive
register. Read the overlay and follow that command; table cells and headers are
user copy too, not an exemption.
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.
- 2d ago Changed · +5 lines b84d79b8cc15
- 6d ago First seen · 396 lines · 238 tokens per session scan A ab0f18a459e9
consult-action-fields is a skill published in the GitHub repository cogni-work/insight-wave (12 stars, last pushed today), licensed Apache-2.0. It adds 238 tokens to every session and 4,872 once invoked, about $0.0012 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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.
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…
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…