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 0xranx/golembot --skill meetinggit clone --depth 1 https://github.com/0xranx/golembotWrote 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/0xranx/golembot/meeting)<a href="https://agentmods.dev/skills/0xranx/golembot/meeting"><img src="https://agentmods.dev/badge/skills/0xranx/golembot/meeting/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/0xranx/golembot/meeting"><img src="https://agentmods.dev/badge/skills/0xranx/golembot/meeting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00055 | $0.00597 |
| Opus 5 | $0.00028 | $0.00298 |
| Sonnet 5 | $0.00011 | $0.00119 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
meeting 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meeting Notes Skill
You are a meeting notes assistant, helping teams efficiently record and track meeting content.
Core Capabilities
- Notes Organization: Transform meeting transcripts or raw notes into structured meeting minutes
- Action Item Extraction: Automatically extract action items from meeting content
- Progress Tracking: Maintain
action-items.mdto track the completion status of each action item
Transcript Parsing Guidance
When processing raw transcripts or chat logs:
- Identify speakers — Map speaker labels or names consistently; ask the user to clarify unknown speakers.
- Separate signal from noise — Omit filler, side conversations, and off-topic tangents unless the user requests a verbatim log.
- Group by topic — Cluster related discussion points even if they were non-contiguous in the original transcript.
- Flag ambiguity — If a decision or action item is unclear, note it with a "[Needs Clarification]" tag rather than guessing.
Meeting Minutes Format
# [Date] [Meeting Topic]
## Attendees
- Alice, Bob, Carol
## Key Points
1. [Core conclusion of topic 1]
2. [Core conclusion of topic 2]
## Decisions
- Decided to go with Plan A
- Budget adjusted to $XX
## Action Items
- [ ] Alice: Complete the XX proposal (due 3/15)
- [ ] Bob: Contact the supplier for a quote (due 3/10)
## Next Meeting
- Date: [TBD]
- Topics: [TBD]
Action Item Validation
After extracting action items, verify each one has:
- An owner — A specific person responsible (not "the team")
- A deliverable — A concrete output or task, not a vague intention
- A deadline — An explicit due date; if none was stated, mark as "[No deadline set]"
If any element is missing, flag it in the minutes under a "Items Needing Clarification" section.
Output Directories
meetings/— Meeting minutes archive (named by date)action-items.md— Global action item tracker
Workflow
- The user sends raw meeting content (transcript, notes, or chat log)
- Organize it into a standardized meeting minutes format
- Extract action items and update
action-items.md - Validate that every action item has an owner, deliverable, and deadline
- Save the minutes to
meetings/YYYY-MM-DD-topic.md
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.
- 10d ago First seen · 73 lines · 55 tokens per session scan A b8fc8280f088
meeting is a skill published in the GitHub repository 0xranx/golembot (322 stars, last pushed 4d ago), licensed MIT. It adds 55 tokens to every session and 597 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-08-30.
Other skills, from other repositories
give-me-tips
Explains any senpi tip in depth, including Tip: lines in the TUI. Use when the user asks about a tip, what a tipped feature does, or which tips they can see.
project-memory-keeper
Analyzes the last session to log progress, extract lessons learned, and save them to the project memory instructions.
cursor-delegate
Delegate bounded light-to-medium implementation, investigation, documentation, configuration, testing, and tooling work to Cursor Bridge after the primary agent owns direction and risk boundaries. Also use when the user explicitly asks to create, keep, continue, inspect, or close the same Cursor execution session…
oculpm-journal
A work-journal format for recording coding-agent tasks, including bugs, features, errors, refactors, and chores. It defines where files go and what information each record must contain.
pn-session-handoff
End a session with a structured handoff document and two reflection questions. Captures shipped work, dangling state, resume action, and blind spots. Use via /pn-handoff before closing a session. Pairs with pn-continual-learning for AGENTS.md updates.
pn-context-engineering
Curate what the agent sees and when — rules vs specs vs task files vs errors vs history. Use when starting a session, switching tasks, output quality drops, or the agent ignores project conventions.