communicate-consulting-message

communicate-consulting-message is a skill for Codex from Rkamirage/consulting-research-to-output. It costs 109 tokens per session (837 once invoked), scanned A, original, MIT.

A guide for turning an approved consulting conclusion into a short, clear message for a meeting, email, update, or presentation.

In plain words
What is it for?
Use it to communicate recommendations, diagnoses, progress, risks, options, lessons, or operating instructions without changing the underlying conclusion.
Why use it?
It keeps the message aligned with the available evidence, audience, uncertainty, and required decision or next step.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: $skill-name invocation.

Good fit Use it to communicate recommendations, diagnoses, progress, risks, options, lessons, or operating instructions without changing the underlying conclusion.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rkamirage/consulting-research-to-output/communicate-consulting-message
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 Rkamirage/consulting-research-to-output --skill communicate-consulting-message
Clone the repo
git clone --depth 1 https://github.com/Rkamirage/consulting-research-to-output

Made for: 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 communicate-consulting-message

README.md
[![agentmods](https://agentmods.dev/badge/skills/rkamirage/consulting-research-to-output/communicate-consulting-message/github.svg)](https://agentmods.dev/skills/rkamirage/consulting-research-to-output/communicate-consulting-message)
Your own site
<a href="https://agentmods.dev/skills/rkamirage/consulting-research-to-output/communicate-consulting-message"><img src="https://agentmods.dev/badge/skills/rkamirage/consulting-research-to-output/communicate-consulting-message/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 communicate-consulting-message

Your own site · 80×15
<a href="https://agentmods.dev/skills/rkamirage/consulting-research-to-output/communicate-consulting-message"><img src="https://agentmods.dev/badge/skills/rkamirage/consulting-research-to-output/communicate-consulting-message.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 109 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 837 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.00109 $0.00837
Opus 5 $0.00055 $0.00418
Sonnet 5 $0.00022 $0.00167
Haiku 4.5 $0.00011 $0.00084

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

Security

Grade A, and why

communicate-consulting-message 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.

skills/communicate-consulting-message/SKILL.md · 54 lines

How it starts

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

Communicate Consulting Message

Express an approved answer clearly. Do not use wording to repair unresolved evidence, change a hypothesis result, or manufacture action.

Confirm the handoff

Require the approved conclusion/status, proof and uncertainty, claim state, communication job, any real decision/action/threshold/learning gate, and Audience/Onboarding Contract locator. Return the smallest unresolved gap to the central lead; do not reconstruct an answer from raw evidence.

Choose the family and close

Select recommendation/decision, diagnosis, insight, status/progress, risk/warning, options/trade-off, learning/validation, or operating instruction.

governing message → basis → implication → family-appropriate close

The close may be a takeaway, current state, threshold, next learning gate, instruction, escalation, decision, or explicit no decision requested. Require authority, owner, or date only when a real approval, commitment, assigned action, or time-critical escalation is requested.

Preserve claim state and audience

Act as the single owner of expression rules for claim state:

  • Facts and supported conclusions may be declarative.
  • Estimates use We estimate...; targets use Target....
  • Unvalidated propositions use Hypothesis: ... or Test whether....
  • Recommendations use Recommend...; material uncertainty stays beside the claim.
  • Use causal wording only for an approved causal claim; otherwise use bounded association.

Apply the received audience contract: explain an unfamiliar company by what it is and why it matters, define unfamiliar concepts before acronyms, honor the new-noun budget, and cold-read consequential standalone messages. Audience variants may change relevance, order, vocabulary, detail, and an authority-consistent close; they may not change the fact, scope, period, unit, confidence, caveat, status, or decision boundary.

Use the complete family-specific decision object in message-patterns.md only for pilot/validation decisions, recurring status/weekly updates, or another operating message that needs it. Do not add an approval object to an informational update.

Read the full file on GitHub · 54 lines

Files

What ships with it

5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 · 54 lines · 109 tokens per session scan A 3b7f5fe3638a

Subscribe to this mod's changes

communicate-consulting-message is a skill published in the GitHub repository Rkamirage/consulting-research-to-output (4 stars, last pushed 1mo ago), licensed MIT. It adds 109 tokens to every session and 837 once invoked, about $0.0005 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

html-ppt

For consulting delivery work: turn diagnosis, frameworks, and project work into a client-adoptable action plan. Built around the core query "consulting-final-deck", with engagement manager judgment, buyer-ready proof, and this outcome: accept the recommendation and commit owners to the roadmap.

nexu-io/open-design · 61 tokens

html-ppt-zhangzara-soft-editorial

A digital-transformation roadmap for a legacy insurer — the diagnosis, the sequenced bets, and the operating rhythm to land them. Built as a decision-grade consulting deck for client executives.

nexu-io/open-design · 49 tokens

html-ppt-zhangzara-mat

A margin-recovery diagnosis for a regional grocery chain — the governing thought, the driver tree, the priorities, and the roadmap. Built as a decision-grade consulting deck for client sponsor, steering committee.

nexu-io/open-design · 51 tokens

huashu-golden-circle

A brand-repositioning strategy for a heritage coffee chain — why, how, what — the governing idea and the moves to prove it. Built as a decision-grade consulting deck for client CMO, board.

nexu-io/open-design · 49 tokens

huashu-luxe-whitespace

A market-entry study for a luxury skincare brand entering Asia — segmentation, positioning, channel, and the phased plan. Built as a decision-grade consulting deck for client leadership.

nexu-io/open-design · 42 tokens

ppt-keynote

An operating-model redesign for a scaling logistics firm — the diagnosis, the target model, and the transition roadmap. Built as a decision-grade consulting deck for client sponsor, ops leaders.

nexu-io/open-design · 40 tokens