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 agentmods add skills/bguivarch/skillforge/meeting-notesnpx skills add bguivarch/skillforge --skill meeting-notesgit clone --depth 1 https://github.com/bguivarch/skillforgeWrote 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/bguivarch/skillforge/meeting-notes)<a href="https://agentmods.dev/skills/bguivarch/skillforge/meeting-notes"><img src="https://agentmods.dev/badge/skills/bguivarch/skillforge/meeting-notes.svg" alt="Measured on agentmods" 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 | $0.00012 | $0.00279 |
| Opus 5 | $0.00006 | $0.00139 |
| Sonnet 5 | $0.00002 | $0.00056 |
| Haiku 4.5 | $0.00001 | $0.00028 |
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 3d 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.
What it actually says
Meeting Notes Summarizer
Transform raw meeting notes or transcripts into clear, actionable summaries.
Output Structure
Meeting Overview
- Date: [Extract or infer date]
- Participants: [List attendees]
- Duration: [If mentioned]
- Purpose: [Brief statement of meeting goal]
Key Discussion Points
Summarize the main topics discussed, organized by theme or agenda item.
Decisions Made
List any decisions that were finalized during the meeting:
- Decision 1
- Decision 2
Action Items
Create a clear action item list with:
- Task description - Owner: @person - Due: date
- Task description - Owner: @person - Due: date
Open Questions
List any unresolved questions or items that need follow-up:
- Question 1 - Who needs to answer?
- Question 2 - When will this be resolved?
Next Steps
- Outline what happens next
- Include next meeting date if scheduled
Guidelines
- Use bullet points for easy scanning
- Bold important names, dates, and deadlines
- Keep summaries concise but complete
- Highlight any blockers or risks mentioned
- If something is unclear, note it as needing clarification
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.
- 3d ago First seen · 46 lines · 12 tokens per session scan A 71274b65fbee
meeting-notes is a skill published in the GitHub repository bguivarch/skillforge (3 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 279 once invoked, about $0.0001 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.
Other skills, from other repositories
offensive-vuln-classes
Exploit development curriculum covering core vulnerability classes with real-world CVE case studies: stack/heap buffer overflows, use-after-free, integer overflows, format strings, type confusion, and race conditions. Use when learning or teaching vuln classes, researching specific CVE patterns, or building exploit…
offensive-mitigations
Security mitigation reference and bypass catalog: ASLR, DEP/NX, RELRO, stack canaries, CFI, sandboxing, seccomp. Covers both detection of enabled mitigations and known bypass techniques. Use when assessing target hardening or planning exploit mitigation bypasses.
offensive-exploit-development
Exploit development operational guide: environment setup, debugging workflow, PoC development lifecycle, writing reliable exploits, using pwntools/pwndbg, heap exploitation techniques, and weaponization considerations. Use when actively developing exploits or setting up an exploit dev environment.
offensive-advanced-redteam
Comprehensive red team operations methodology covering full engagement lifecycle from planning through reporting. Addresses engagement scoping and rules of engagement negotiation, multi-tier C2 infrastructure design with redirectors and domain fronting, malleable traffic profiles and beacon tradecraft, OPSEC…
offensive-social-engineering
Social engineering attack techniques beyond email phishing for authorized red team and physical penetration testing engagements. Covers pretexting methodology (persona creation, authority and urgency psychological triggers, rapport building), vishing (voice phishing via caller ID spoofing, IVR system exploitation…
offensive-dependency-confusion
Deep-dive offensive methodology for dependency confusion and namespace attacks across all major package ecosystems. Covers npm scope confusion exploiting the gap between public and private scoped packages and .npmrc misconfigurations where registry mappings fail to pin internal scopes exclusively. Addresses PyPI…