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 Dokkabei97/forged-claude-code --skill meeting-notesgit clone --depth 1 https://github.com/Dokkabei97/forged-claude-codeWrote 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/dokkabei97/forged-claude-code/meeting-notes)<a href="https://agentmods.dev/skills/dokkabei97/forged-claude-code/meeting-notes"><img src="https://agentmods.dev/badge/skills/dokkabei97/forged-claude-code/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.1 | $0.00051 | $0.01587 |
| Opus 5 | $0.00026 | $0.00794 |
| Sonnet 5 | $0.00010 | $0.00317 |
| Haiku 4.5 | $0.00005 | $0.00159 |
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 6d 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meeting Notes - Structured Meeting Records
Overview
Generates consistent, actionable meeting notes that capture decisions and drive follow-up. Because "I thought we decided..." should never happen.
1. When to Apply
| Trigger | Behavior |
|---|---|
| "meeting notes", "회의록" | Interactive meeting type selection |
| "standup" | Daily standup template |
| "sprint" | Sprint planning/review template |
| "board meeting" | Board meeting template |
| "1:1" | 1-on-1 meeting template |
2. Meeting Templates
General Meeting Template
# Meeting: [Title]
| Item | Detail |
|------|--------|
| **Date** | YYYY-MM-DD HH:MM |
| **Duration** | [X] minutes |
| **Attendees** | @name1, @name2, @name3 |
| **Facilitator** | @name |
| **Note-taker** | @name |
---
## Agenda
1. [Topic 1] — [Owner] — [Time allocation]
2. [Topic 2] — [Owner] — [Time allocation]
3. [Topic 3] — [Owner] — [Time allocation]
---
## Discussion Notes
### 1. [Topic 1]
- [Key point discussed]
- [Different viewpoint raised by @name]
- **Decision**: [What was decided]
- **Rationale**: [Why this was decided]
### 2. [Topic 2]
- [Key point discussed]
- **Decision**: [What was decided]
---
## Decisions Made
| # | Decision | Rationale | Decided By |
|---|----------|-----------|------------|
| D1 | [Decision] | [Why] | [Who] |
| D2 | [Decision] | [Why] | [Who] |
## Action Items
| # | Action | Owner | Due Date | Status |
|---|--------|-------|----------|--------|
| A1 | [Task] | @name | YYYY-MM-DD | ⬜ |
| A2 | [Task] | @name | YYYY-MM-DD | ⬜ |
## Parking Lot (다음에 논의)
- [Topic deferred to future discussion]
---
*Next meeting: YYYY-MM-DD HH:MM*
Daily Standup Template
# Standup — YYYY-MM-DD
## @name1
- **Yesterday**: [completed tasks]
- **Today**: [planned tasks]
- **Blockers**: [issues needing help] / None
## @name2
- **Yesterday**: [completed tasks]
- **Today**: [planned tasks]
- **Blockers**: [issues needing help] / None
---
**Team Blockers Summary:**
- [Blocker] → Owner: @name → ETA: [date]
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.
- 6d ago First seen · 242 lines · 51 tokens per session scan A 203719e9bd75
meeting-notes is a skill published in the GitHub repository Dokkabei97/forged-claude-code (2 stars, last pushed 6mo ago), licensed MIT. It adds 51 tokens to every session and 1,587 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-31.
Other skills, from other repositories
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
mcporter
List, auth, and call MCP servers/tools from the terminal.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
telegram-setup
Connect a Telegram bot to the Vellum Assistant gateway with automated webhook registration and credential storage.