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-project-plan)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/consult-project-plan"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/consult-project-plan.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.00233 | $0.03235 |
| Opus 5 | $0.00117 | $0.01618 |
| Sonnet 5 | $0.00047 | $0.00647 |
| Haiku 4.5 | $0.00023 | $0.00324 |
Grade A, and why
consult-project-plan 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 4d 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Consult Project Plan
Render a phased roadmap of the engagement's work-breakdown structure — when each
deliverable can start, how much effort it carries, who owns it, which points are
milestones, and which deliverables sit on the critical path — as a persisted
project-plan.md markdown artifact at the engagement root. It is the timeline
sibling of consult-dashboard (visual status) and consult-resume (next-action
recommender): a read-mostly view that turns the deliverable graph plus the
scheduling fields into a sequenced plan a consultant can browse in Obsidian.
Core Concept
Schedule lives on each deliverable inside its field.json entry — the five
optional scheduling fields start_date, due_date, duration, owner,
milestone (see $CLAUDE_PLUGIN_ROOT/references/project-plan-model.md). A phased
timeline is derived, never stored: the roadmap phases are the topological
layers of the depends_on[] graph (layer 0 = deliverables with no in-plan
dependency; layer N = deliverables whose dependencies all sit in layers < N), and
the duration-weighted forward pass + critical path come from
deliverable-graph.py <engagement-dir> schedule. This skill only reads that state
and writes project-plan.md; it never mutates a field.json, never writes a
duration-derived date back into engagement state, and never edits a deliverable's
schedule. Populating the scheduling fields is the job of consult-action-fields
(the plan-editing surface), not this skill.
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.
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.
- 4d ago Changed · +5 lines e240409de9b2
- 8d ago First seen · 248 lines · 233 tokens per session scan A 9af1ad2139cc
consult-project-plan is a skill published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed today), licensed Apache-2.0. It adds 233 tokens to every session and 3,235 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.