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.
npx skills add hollandkevint/data-product-operator --skill healthcare-data-readiness-debriefgit clone --depth 1 https://github.com/hollandkevint/data-product-operatorWrote 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/hollandkevint/data-product-operator/healthcare-data-readiness-debrief)<a href="https://agentmods.dev/skills/hollandkevint/data-product-operator/healthcare-data-readiness-debrief"><img src="https://agentmods.dev/badge/skills/hollandkevint/data-product-operator/healthcare-data-readiness-debrief/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.
<a href="https://agentmods.dev/skills/hollandkevint/data-product-operator/healthcare-data-readiness-debrief"><img src="https://agentmods.dev/badge/skills/hollandkevint/data-product-operator/healthcare-data-readiness-debrief.svg" alt="Reviewed on agentmods" width="80" 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.00059 | $0.02321 |
| Opus 5 | $0.00030 | $0.01161 |
| Sonnet 5 | $0.00012 | $0.00464 |
| Haiku 4.5 | $0.00006 | $0.00232 |
Grade A, and why
healthcare-data-readiness-debrief 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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Healthcare Data Readiness Debrief
Help a healthcare data professional answer: What made this project's data preparation hard, what remains unresolved, and what should we check next?
Work on one project and one intended use. A retrospective can end with lessons for the next project. An active project should end with an evidence request or check that helps its owner make the next decision.
Using this file
Read the questions as a worksheet, or give this file and the relevant linked reference to your team's approved AI assistant. Start with an approved summary of one project. Ask for one question at a time, or request a brief from the summary. Say “brief now” to stop the interview. No patient records or database access are needed.
The output is a short brief with the intended use, what happened, unresolved questions, next checks and owners to confirm. The instructions below guide the assistant; you do not need to answer every question in this file.
See a complete fictional brief · Browse synthetic scenarios · Setup and testing limits · Install in Codex or Claude Code · Full skill library
Keep the supporting files with this skill. If your assistant cannot open a reference, supply that file separately. No other skill or plugin is required. Use approved summaries or synthetic examples, not patient records, credentials, confidential contracts or restricted study materials. This debrief does not audit a dataset or approve a launch. Your chosen assistant's data-handling rules still apply.
Instructions for the assistant
Start with their account
Read any supplied summary first. If it answers a question below, do not ask it again. If nothing was supplied, open with:
“What was someone supposed to be able to do with the data in the project you want to review?”
Ask one question per turn. Follow the uncertainty that most affects the intended use. Offer a brief after a few useful exchanges, but do not hide a material dependency to meet a question limit. If the user requests a brief now, produce it without restarting intake. Accept “unknown” and put it in the output with a way to resolve it.
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.
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.
- yesterday Changed · +10 lines 9237254d00c9
- 3d ago First seen · 120 lines · 59 tokens per session scan A c7543f81fbef
healthcare-data-readiness-debrief is a skill published in the GitHub repository hollandkevint/data-product-operator (3 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 2,321 once invoked, about $0.0003 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-09-09.
Other skills, from other repositories
fechar-dia
Fecha o dia de trabalho. Avalia as 3 do dia, classifica o que não fechou, semeia o movimento.
processar-reuniao
Transforma uma reunião que aconteceu em nota estruturada e propaga o que importa. A pessoa cola a transcrição, o resumo automático ou as notas cruas. Use quando a pessoa disser "processa essa reunião", "processa esse 1:1", "olha o que rolou na reunião", colar uma transcrição pedindo organização, ou…
preparar-conversa
Monta a pauta antes de uma conversa que importa. 1:1 com liderado, 1:1 com o próprio líder, alinhamento com par ou stakeholder. Use quando a pessoa disser "prepara o 1:1 com [nome]", "monta a pauta", "vou falar com [nome]", "tenho reunião com [nome], me prepara", "/preparar-conversa". NÃO use pra processar a conversa…
classify
Assess or re-assess the innovation-vs-implementation classification and 0-100 innovation weight for one feature or the whole Product/Features set, then regenerate the ranked features-index.md and run the portfolio sanity check. Use when features need (re)ranking or after editing the UVP.
feature
Create or revise a single Product feature file with a complete user story, Given/When/Then acceptance criteria, and an innovation-vs-implementation classification. Use when adding one feature to Product/Features/, or refining an existing feature, outside a full /innovate run.
iflow
The front door / orchestrator for the I-Framework. Reads the Product/ folder, determines which stage (Intent, Ideation, Innovation) you're in from the artifacts and their gates, reports the risk-burndown state, and routes you to the next step. Use to start or resume the Intent → Ideation → Innovation flow.