owner-facing-reporting

owner-facing-reporting is a skill for Codex from ConnorRX56/presentation-delivery-skills. It costs 76 tokens per session (1,154 once invoked), scanned A, original, MIT.

A writing guide for giving progress updates and explaining problems in terms the person responsible for the work can understand.

In plain words
What is it for?
It helps write status reports, estimates, reviews, acceptance updates, and completion reports that explain the visible result and any remaining gap.
Why use it?
It prevents technical logs, test results, and internal labels from hiding whether the work is finished, usable, or still blocked.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit It helps write status reports, estimates, reviews, acceptance updates, and completion reports that explain the visible result and any remaining gap.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/connorrx56/presentation-delivery-skills/owner-facing-reporting
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 ConnorRX56/presentation-delivery-skills --skill owner-facing-reporting
Clone the repo
git clone --depth 1 https://github.com/ConnorRX56/presentation-delivery-skills

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 owner-facing-reporting

README.md
[![agentmods](https://agentmods.dev/badge/skills/connorrx56/presentation-delivery-skills/owner-facing-reporting/github.svg)](https://agentmods.dev/skills/connorrx56/presentation-delivery-skills/owner-facing-reporting)
Your own site
<a href="https://agentmods.dev/skills/connorrx56/presentation-delivery-skills/owner-facing-reporting"><img src="https://agentmods.dev/badge/skills/connorrx56/presentation-delivery-skills/owner-facing-reporting/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 owner-facing-reporting

Your own site · 80×15
<a href="https://agentmods.dev/skills/connorrx56/presentation-delivery-skills/owner-facing-reporting"><img src="https://agentmods.dev/badge/skills/connorrx56/presentation-delivery-skills/owner-facing-reporting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,154 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00076 $0.01154
Opus 5 $0.00038 $0.00577
Sonnet 5 $0.00015 $0.00231
Haiku 4.5 $0.00008 $0.00115

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

Security

Grade A, and why

owner-facing-reporting 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.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/check_owner_report.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/owner-facing-reporting/SKILL.md · 87 lines

How it starts

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

Owner-Facing Reporting

Role

Report to the person who owns the result, not to another implementation specialist. The owner must be able to decide whether the work is finished, usable, wrong, or waiting on something without decoding logs, stage names, hashes, buffer counts, or internal architecture.

This skill controls communication, not evidence standards. Keep the technical proof, but put it after the human result. If the operator explicitly asks for raw technical detail, still give the direct owner-level answer first, then expand.

Input Contract

Collect the actual goal, current status, final visible or operational result, remaining gap, user impact, next action, and supporting evidence. For visible work, also collect the fresh target-application capture and the agent's own visual inspection result.

Do not treat a build, test, hash, binding count, pipeline stage, or reviewer message as the result itself. Determine what that fact means for what a person can see, use, approve, or reject.

Workflow

  1. Answer the exact question in the first sentence: finished or not, usable or not, and the one decisive reason.
  2. State what the owner can see or do now. For visual work, describe the actual model, pose or motion, framing, materials and color, light and shadow, transparency, clarity, missing content, or visible defect that was personally inspected in the fresh target result.
  3. State what remains and why it matters to the final goal. Translate every technical blocker into its visible or operational consequence.
  4. State the next action and whether the owner needs to do anything. Do not hand ordinary QA back to the owner.
  5. Put implementation details, identifiers, counts, logs, hashes, and file paths last, and include only details that support a decision or were explicitly requested.

Useful translation pattern:

technical fact -> what it changes for the owner -> current decision

For time estimates, give a range tied to the remaining concrete outcome and name the largest uncertainty. Do not inflate an estimate by counting already-finished work.

Read the full file on GitHub · 87 lines

Files

What ships with it

6 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 · 87 lines · 76 tokens per session scan A 28e5e32a5f86

Subscribe to this mod's changes

owner-facing-reporting is a skill published in the GitHub repository ConnorRX56/presentation-delivery-skills (11 stars, last pushed 17d ago), licensed MIT. It adds 76 tokens to every session and 1,154 once invoked, about $0.0004 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

tasteful-ui

UI design and implementation for real product surfaces with taste-first critique, reference routing, project-specific design briefs, variation comparison, and implementation verification. Use when Codex should redesign, build, polish, or critique frontend UI by reading project context, exploring taste, routing through…

DonkeyKing01/tasteful-ui-skill · 132 tokens

baoyu-youtube-transcript

A tool for downloading the written captions, subtitles, chapter information, speaker labels, and cover image from a YouTube video using its URL or ID.

JimLiu/baoyu-skills · 107 tokens

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…

nexu-io/open-design · 117 tokens

motion-frames

A single-frame motion-design composition with looping CSS animations — rotating type ring, animated globe, ticking timer, parallax labels. Renders as a hero video poster you can hand straight to HyperFrames or any keyframe-based exporter. Use when the brief asks for "motion design", "animated hero", "loop", "video…

nexu-io/open-design · 91 tokens

wireframe-annotated

An annotated / redline lo-fi wireframe — a desktop landing/marketing page drawn as flat greyboxes inside a browser chrome frame, overlaid with numbered annotation pins (①②③④⑤) in a single accent color, paired with a right-hand SPEC PANEL that lists each numbered pin with a short engineering / UX note. This is the…

nexu-io/open-design · 155 tokens

hr-onboarding

A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".

nexu-io/open-design · 62 tokens