agentmods.dev

engagement-report-conventions

engagement-report-conventions is a skill for Claude Code from microsoft/hve-core. It costs 41 tokens per session (1,261 once invoked), scanned A, original, MIT.

A style and data-handling guide for producing engagement reports and their source files. It defines wording, formatting, and reporting conventions for different audiences.

In plain words
What is it for?
It helps generate reports, manage report inputs, and maintain the related engagement.yaml configuration file.
Why use it?
It prevents inconsistent language, unsupported claims, and formatting mistakes across reports produced by an agent.

Skill for Claude Code ✓ vendor

Written for Claude Code: user-invocable in frontmatter. Also seen: mentions subagents.

not rated 1.6krepo +14 today A scan 41 tokens original MIT

Good fit It helps generate reports, manage report inputs, and maintain the related engagement.yaml configuration file.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/microsoft/hve-core/engagement-report-conventions
View source ↗ microsoft/hve-core
About the project

HVE Core is a collection of agents, prompts, coding instructions, and skills for building repeatable software-development workflows with GitHub Copilot. It is intended for individuals and teams that want structured AI-assisted research, planning, implementation, and review, while the catalogue entries provide many of its reusable workflow components.

microsoft/hve-core · 1,606 stars · on GitHub

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 microsoft/hve-core --skill engagement-report-conventions
Clone the repo
git clone --depth 1 https://github.com/microsoft/hve-core

Made for: Claude Code.

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 engagement-report-conventions

README.md
[![agentmods](https://agentmods.dev/badge/skills/microsoft/hve-core/engagement-report-conventions/github.svg)](https://agentmods.dev/skills/microsoft/hve-core/engagement-report-conventions)
Your own site
<a href="https://agentmods.dev/skills/microsoft/hve-core/engagement-report-conventions"><img src="https://agentmods.dev/badge/skills/microsoft/hve-core/engagement-report-conventions/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 engagement-report-conventions

Your own site · 80×15
<a href="https://agentmods.dev/skills/microsoft/hve-core/engagement-report-conventions"><img src="https://agentmods.dev/badge/skills/microsoft/hve-core/engagement-report-conventions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,261 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.00041 $0.01261
Opus 5.5 $0.00016 $0.00504
Sonnet 5.5 $0.00008 $0.00252
Haiku 4.5 $0.00004 $0.00126

Measured yesterday against content hash 2971754c19c0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

engagement-report-conventions 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 yesterday.

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.

.github/skills/engagement-reporting/engagement-report-conventions/SKILL.md · 156 lines

How it starts

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

Engagement Report Conventions

These rules apply to every engagement report, its sources, its working files, and engagement.yaml.

Style Guide

Rules for formatting, tone, and language in engagement reports.

Voice and Tone

  • Use active voice throughout
  • State facts confidently; avoid unsupported hedging
  • Write for the audience's level: tactical for engineers, outcome-focused for directors, strategic for VPs
  • Describe engagement outcomes and decisions, not how the reporting agent found them

Formatting

  • Do not add trailing full stops to bullet fragments
  • Use semicolons to separate related clauses within a bullet
  • Bold module or component names when it improves scanning
  • Include dates for all scheduled events

Language

Do Not Use
  • "deep dive", "sync up", "circle back", "leverage", "robust", "seamless"
  • "&" in prose; write "and"
  • Em dashes for parenthetical explanation; use semicolons or separate sentences
  • AI patterns such as "I'm happy to help", "Let me know if", and "Here's what I found"
  • Research-process phrases such as "primary-source evidence", "available evidence", "the search returned", "the transcript was unavailable", or "requires verification"
  • Source-channel narration such as "Teams chat identified", "meeting notes showed", or "an email confirmed" unless the channel itself is materially relevant to the audience
Evidence Separation

Keep source references, coverage gaps, confidence assessments, retrieval details, and verification notes in .working/ and the agent handoff. In the report:

  • State the supported business outcome directly
  • Convert unresolved facts into a blocker, ask, or next step
  • Omit unsupported detail rather than explaining the retrieval limitation
  • Do not add a Coverage Note, Evidence Note, Research Summary, or source list
Progression

Each update must demonstrate forward movement. Never repeat the same status.

  • Bad: "Continuing work on the API integration" (same as last week)
  • Good: "API integration reached 95% completion; awaiting schema validation from the customer team"

Read the full file on GitHub · 156 lines

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. yesterday First seen · 156 lines · 41 tokens per session scan A 2971754c19c0

Subscribe to this mod's changes

engagement-report-conventions is a skill published in the GitHub repository microsoft/hve-core (1,606 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 1,261 once invoked, about $0.0002 per session on Opus 5.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-11-07.

DocumentsWriting and docs
Related

engagement-report-conventions compared with skills from other repositories

engagement-report-conventions next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
engagement-report-conventionsmicrosoft/hve-coreSkill1.6ktodayMITA41Claude Code
orbit-notionnexu-io/open-designSkill107ktodayApache-2.0A117Claude Code, Codex
instrument-data-to-allotropeanthropics/knowledge-work-pluginsSkill35kyesterdayApache-2.0A123Claude Code
apify-youtube-transcript-scrapersickn33/agentic-awesome-skillsSkill49k2d agoMITA48Claude Code
legal-holdanthropics/claude-for-legalSkill9.9kyesterdayApache-2.0A68Claude Code
report-to-pdfasgeirtj/system_prompts_leaksSkill71ktodayCC0-1.0A17Claude Code, Codex
artifact-template-minimal-letterheadasgeirtj/system_prompts_leaksSkill71ktodayCC0-1.0A54Claude Code, Codex