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 wolfenazz/YzPzCode --skill meeting-notesgit clone --depth 1 https://github.com/wolfenazz/YzPzCodeWrote 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/wolfenazz/yzpzcode/meeting-notes)<a href="https://agentmods.dev/skills/wolfenazz/yzpzcode/meeting-notes"><img src="https://agentmods.dev/badge/skills/wolfenazz/yzpzcode/meeting-notes/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/wolfenazz/yzpzcode/meeting-notes"><img src="https://agentmods.dev/badge/skills/wolfenazz/yzpzcode/meeting-notes.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.00066 | $0.00329 |
| Opus 5.5 | $0.00026 | $0.00132 |
| Sonnet 5.5 | $0.00013 | $0.00066 |
| Haiku 4.5 | $0.00007 | $0.00033 |
Grade A, and why
meeting-notes 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 1mo 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.
This is a copy
100% identical to meeting-notes — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Meeting Notes Skill
Produce a single-screen meeting notes page.
Workflow
- Read DESIGN.md.
- Layout:
- Header: meeting title, date, time, location/Zoom, attendees row.
- Agenda checklist (4–6 items).
- Decisions panel — bulleted list with strong styling.
- Action items table with owner, due date, status.
- "Open questions" + "next meeting" footer.
- Subdued colour palette, clear hierarchy.
Output contract
<artifact identifier="notes-name" type="text/html" title="Meeting Notes">
<!doctype html>...</artifact>
What ships with it
1 file 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.
- 1mo ago First seen · 48 lines · 66 tokens per session scan A 544e1caccfea
meeting-notes is a skill published in the GitHub repository wolfenazz/YzPzCode (20 stars, last pushed yesterday), licensed Apache-2.0. It adds 66 tokens to every session and 329 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to meeting-notes, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
backlog
Read, work, and maintain a repo's deferred-work items in docs/backlog/, one file per item. Use when the user says "backlog", "check backlog", "what's on my backlog", "work the backlog", "address the backlog", "add to backlog", "clean up backlog", or when a review or task produced items that are real but not being…
alive:create-walnut
Something new is emerging. A venture, an experiment, a person entering the orbit, a life area getting serious. It needs its own walnut — its own identity, history, and future. Scaffolds the full structure, maps existing context sources, and optionally migrates files across.
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.
alive-bundle
Create, manage, and graduate bundles -- the unit of focused work within a walnut.
alive-create
Scaffold a new walnut -- venture, experiment, person, life area, project.
alive-project
Regenerate now.json projections for all walnuts (mechanical, no approval needed).