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/curiouslearner/devkit/meeting-notesnpx skills add CuriousLearner/devkit --skill meeting-notesgit clone --depth 1 https://github.com/CuriousLearner/devkitWhat 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.00022 | $0.07669 |
| Opus 5 | $0.00011 | $0.03834 |
| Sonnet 5 | $0.00004 | $0.01534 |
| Haiku 4.5 | $0.00002 | $0.00767 |
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.
How it starts
The opening of the file, as written. The whole thing — 1,082 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meeting Notes Skill
Convert meeting discussions into clear, actionable notes with tasks, decisions, and follow-ups for effective team collaboration.
Instructions
You are a meeting facilitation and documentation expert. When invoked:
-
Capture Meeting Content:
- Key discussion points
- Decisions made
- Action items assigned
- Questions raised
- Parking lot items
- Follow-up needed
-
Structure Notes:
- Clear formatting and sections
- Searchable and scannable
- Chronological flow
- Linked to related resources
- Tagged for discoverability
-
Extract Action Items:
- Specific tasks with owners
- Clear deadlines
- Acceptance criteria
- Dependencies noted
- Priority indicated
-
Highlight Decisions:
- What was decided
- Why it was decided
- Who decided (if relevant)
- Impact and implications
- Next steps
-
Enable Follow-Through:
- Share notes promptly (within 24h)
- Track action items
- Link to project management tools
- Schedule follow-ups
- Archive for future reference
Meeting Notes Templates
Standard Meeting Notes Template
# [Meeting Title]
**Date**: January 15, 2024
**Time**: 2:00 PM - 3:00 PM EST
**Location**: Zoom / Conference Room A
**Note Taker**: [Your Name]
## Attendees
**Present**:
- Alice Johnson (Engineering Manager)
- Bob Smith (Backend Lead)
- Carol Williams (Frontend Lead)
- David Brown (Product Manager)
**Absent**:
- Eve Davis (On PTO)
**Guests**:
- Frank Miller (Security Team)
---
## Agenda
1. Q1 Planning Review
2. Security Audit Findings
3. Performance Issues Discussion
4. Team Capacity Planning
---
## Discussion Summary
### 1. Q1 Planning Review (15 min)
**Context**: Review progress on Q1 objectives.
**Discussion**:
- Successfully launched user dashboard (Q1 OKR #1) ✅
- Payment integration delayed by 2 weeks due to compliance requirements
- Mobile app beta at 80% completion (target: 100% by end of Q1)
**Key Points**:
- Dashboard has 85% user adoption (exceeds 70% target)
- Payment delay won't affect Q1 goals - can slip to early Q2
- Mobile beta needs additional testing resources
**Metrics Reviewed**:
| Objective | Target | Current | Status |
|-----------|--------|---------|--------|
| User Dashboard Launch | 70% adoption | 85% adoption | ✅ On Track |
| Payment Integration | Q1 | Q2 Week 1 | ⚠️ Slight Delay |
| Mobile Beta | 100% | 80% | ⚠️ At Risk |
---
### 2. Security Audit Findings (20 min)
**Presenter**: Frank Miller
**Findings**:
1. **Critical**: JWT tokens not rotating after password change
2. **High**: Missing rate limiting on authentication endpoints
3. **Medium**: Outdated dependencies with known vulnerabilities
4. **Low**: Missing security headers on some API responses
**Discussion**:
- Critical issue is a security risk - needs immediate fix
- Rate limiting should be implemented before next release
- Dependency updates can be automated with Renovate bot
- Security headers are quick wins
**Questions Raised**:
- Q: Should we implement 2FA? (Parking lot - discuss in separate meeting)
- Q: Timeline for security headers? A: Can complete in current sprint
---
### 3. Performance Issues Discussion (15 min)
**Context**: Users reporting slow dashboard load times.
**Identified Issues**:
- Database queries not optimized (N+1 query problem)
- Large bundle size (2.5MB, target: <1MB)
- Missing CDN for static assets
- No caching layer for frequently accessed data
**Root Causes**:
- Recent feature additions didn't include performance testing
- No bundle size monitoring in CI/CD
- Infrastructure not updated since launch
**Proposed Solutions**:
1. Add database indexes and optimize queries
2. Implement code splitting and lazy loading
3. Set up CloudFront CDN
4. Add Redis caching layer
5. Establish performance budgets in CI
---
### 4. Team Capacity Planning (10 min)
**Discussion**:
- Eve on PTO next week (Jan 22-26)
- Bob has oncall rotation (Jan 15-22)
- Carol starting new project Feb 1
- Need to hire 2 more engineers by Q2
**Impact on Current Sprint**:
- May need to reduce sprint commitment
- Security fixes take priority
- Nice-to-have features can be deferred
---
## Decisions Made
### ✅ Decision 1: Prioritize Security Fixes
**Decision**: Address critical and high-severity security issues immediately, delaying feature work if necessary.
**Rationale**: Security risks outweigh feature velocity. Customer trust is paramount.
**Impact**:
- Current sprint scope reduced by 20%
- Feature "Advanced Filtering" moved to next sprint
- All engineers to review security best practices
**Owner**: Bob (Backend Lead)
**Timeline**: Critical fix by EOW (Jan 19), High-severity by Jan 26
---
### ✅ Decision 2: Implement Performance Budgets
**Decision**: Add automated performance checks to CI/CD pipeline.
**Metrics**:
- Bundle size: max 1MB gzipped
- Lighthouse performance score: min 90
- API response time: p95 < 500ms
- Database query time: p95 < 100ms
**Impact**: PRs failing budgets will require performance review before merge.
**Owner**: Carol (Frontend Lead) + Bob (Backend Lead)
**Timeline**: Implement by Feb 1
---
### ✅ Decision 3: Hire Additional Engineers
**Decision**: Open 2 requisitions (1 Backend, 1 Frontend) for Q2 start.
**Rationale**: Current team at 110% capacity, affecting sustainability and innovation time.
**Next Steps**:
- David to work with recruiting on job descriptions
- Alice to define interview process
- Target start date: April 1
**Owner**: Alice (Engineering Manager)
**Timeline**: Job posts live by Jan 22
---
## Action Items
### Priority 1 (This Week)
- [ ] **[Bob]** Fix JWT rotation vulnerability
- **Due**: Jan 19 (EOW)
- **Acceptance Criteria**: JWT invalidated on password change, tested in staging
- **Dependencies**: None
- **Estimate**: 4 hours
- [ ] **[Carol]** Analyze bundle size and create reduction plan
- **Due**: Jan 18
- **Deliverable**: Document with specific reduction strategies
- **Dependencies**: None
- **Estimate**: 2 hours
- [ ] **[Alice]** Share security audit report with team
- **Due**: Jan 16 (today)
- **Format**: Slack #engineering + detailed Confluence doc
- **Dependencies**: None
- **Estimate**: 30 minutes
### Priority 2 (This Sprint - by Jan 26)
- [ ] **[Bob]** Implement rate limiting on auth endpoints
- **Due**: Jan 26
- **Acceptance Criteria**:
- Max 5 login attempts per 15 minutes
- Clear error messages to users
- Documented in API docs
- **Dependencies**: None
- **Estimate**: 1 day
- [ ] **[David]** Set up automated dependency updates (Renovate)
- **Due**: Jan 26
- **Acceptance Criteria**:
- Auto-PR for patch updates
- Weekly digest for minor updates
- Manual review for major updates
- **Dependencies**: DevOps approval
- **Estimate**: 4 hours
- [ ] **[Carol]** Implement code splitting for dashboard
- **Due**: Jan 26
- **Acceptance Criteria**: Reduce initial bundle from 2.5MB to <1MB
- **Dependencies**: Bundle analysis complete
- **Estimate**: 2 days
### Priority 3 (Next Sprint - by Feb 9)
- [ ] **[Bob]** Add database indexes and optimize queries
- **Due**: Feb 9
- **Acceptance Criteria**: N+1 queries eliminated, p95 query time <100ms
- **Dependencies**: Performance testing environment
- **Estimate**: 3 days
- [ ] **[DevOps - Taylor]** Set up CloudFront CDN for static assets
- **Due**: Feb 9
- **Acceptance Criteria**: All images/CSS/JS served from CDN
- **Dependencies**: AWS account access
- **Estimate**: 1 day
- [ ] **[Bob + Carol]** Implement performance budgets in CI
- **Due**: Feb 1
- **Acceptance Criteria**: CI fails if budgets exceeded
- **Dependencies**: Metrics defined
- **Estimate**: 1 day
### Future / Parking Lot
- [ ] **[TBD]** Evaluate 2FA implementation
- **Due**: TBD (separate discussion needed)
- **Owner**: To be assigned
- **Note**: Schedule dedicated security features meeting
- [ ] **[Alice]** Complete hiring process
- **Due**: Target April 1 start dates
- **Milestones**:
- Jan 22: Job posts live
- Feb 15: First round interviews
- Mar 1: Final candidates selected
- Apr 1: Start date
---
## Key Metrics & Data
**Performance Baseline (before fixes)**:
- Dashboard load time: 4.2s (target: <2s)
- Bundle size: 2.5MB (target: <1MB)
- API p95 response time: 850ms (target: <500ms)
- Database query p95: 340ms (target: <100ms)
**Security Audit Summary**:
- Critical issues: 1
- High severity: 1
- Medium severity: 3
- Low severity: 5
**Team Capacity (Current Sprint)**:
- Total story points: 45
- Committed: 50 (110% capacity)
- Recommended reduction: 10 points
- New commitment: 40 points
---
## Parking Lot
Items discussed but deferred to later:
1. **Two-Factor Authentication (2FA)**
- Needs: Security team input, user research
- Timeline: Discuss in Q2 planning
- Owner: TBD
2. **Mobile App Marketing Strategy**
- Needs: Product and marketing alignment
- Timeline: After beta completion
- Owner: David (Product)
3. **Team Offsite Planning**
- Needs: Budget approval
- Timeline: Q2 (April-June)
- Owner: Alice
---
## Questions & Answers
**Q**: Should we pause new features entirely for security fixes?
**A**: No, but security takes priority. Reduce scope but maintain momentum.
**Q**: Can we hire contractors for short-term capacity?
**A**: Parking lot - discuss budget and approval process with leadership.
**Q**: Who will handle performance monitoring post-implementation?
**A**: Bob and Carol will set up, DevOps will maintain dashboards.
**Q**: What's our rollback plan if CDN causes issues?
**A**: Standard deployment process - canary release with quick rollback capability.
---
## Follow-Up Items
- **Next meeting**: Feb 1, 2024 (2 weeks) - Progress check on action items
- **Alice** to send summary email to broader engineering team by EOD
- **Bob** to schedule security fix review with Frank next week
- **Carol** to present performance improvements at next all-hands
- **All attendees** to review and add any missing items by Jan 16 EOD
---
## Related Resources
- [Security Audit Full Report](https://confluence.company.com/security-audit-jan-2024)
- [Q1 OKR Dashboard](https://jira.company.com/okrs/2024-q1)
- [Performance Metrics Dashboard](https://datadog.company.com/dashboard/performance)
- [Team Capacity Planning Sheet](https://docs.google.com/spreadsheets/capacity-2024)
---
## Notes for Next Meeting
- Review all action items completion status
- Performance metrics comparison (before/after)
- Security audit remediation verification
- Hiring pipeline update
- Team velocity assessment
---
**Notes Compiled By**: [Your Name]
**Shared With**: [email protected], #engineering
**Last Updated**: January 15, 2024 4:30 PM
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 · 1,082 lines · 22 tokens per session scan A b6e009cc46fb
meeting-notes is a skill published in the GitHub repository CuriousLearner/devkit (27 stars, last pushed 10mo ago), licensed MIT. It adds 22 tokens to every session and 7,669 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-30.
Other skills, from other repositories
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
lark-im
飞书即时通讯：收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片（Interactive Card）、监听卡片按钮回调（card.action.trigger）。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶（添加/移除/查询置顶会话）、管理标签数据、处理卡片回调时使用。.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
reflect
Review recent work, find repeated workflow patterns, and suggest reusable skills, agents, commands, config changes, or playbooks. Use when the user asks to learn from past sessions, improve recurring workflows, or identify what should be turned into reusable agent instructions.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
organize-threads
猫猫辅助整理未分类 thread，分析标题和元数据，建议合适的标签。 Use when: 用户说"帮我整理"、"分类 thread"、点击整理按钮。 Not for: 删除/编辑标签本身。 Output: 按 thread 的标签建议列表。.