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 Dannykkh/skill-olympus --skill daily-meeting-updategit clone --depth 1 https://github.com/Dannykkh/skill-olympusWrote 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/dannykkh/skill-olympus/daily-meeting-update)<a href="https://agentmods.dev/skills/dannykkh/skill-olympus/daily-meeting-update"><img src="https://agentmods.dev/badge/skills/dannykkh/skill-olympus/daily-meeting-update/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/dannykkh/skill-olympus/daily-meeting-update"><img src="https://agentmods.dev/badge/skills/dannykkh/skill-olympus/daily-meeting-update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 432 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00045 | $0.03368 |
| Opus 5 | $0.00023 | $0.01684 |
| Sonnet 5 | $0.00009 | $0.00674 |
| Haiku 4.5 | $0.00005 | $0.00337 |
Grade A, and why
daily-meeting-update 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 8d 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 — 448 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daily Meeting Update
Generate a daily standup/meeting update through an interactive interview. Never assume tools are configured—ask first.
Setup (최초 1회)
이 스킬은 config.json에 설정이 필요합니다.
config.json을 읽는다 (skills/daily-meeting-update/config.json또는 현재 CLI의 글로벌 스킬 경로)- 빈 필드가 있으면 현재 CLI의 질문 방식으로 사용자에게 질문한다
- 답변을
config.json에 저장한다 - 이후 실행 시에는
config.json에서 자동으로 읽는다
| 항목 | 설명 | 예시 |
|---|---|---|
github_username |
GitHub 사용자명 (GitHub 연동 시 자동 필터링에 사용) | octocat |
jira_project_key |
기본 Jira 프로젝트 키 | PROJ |
slack_channel |
스탠드업 결과를 공유할 Slack 채널 | #daily-standup |
standup_format |
출력 형식 (markdown / plain) |
markdown |
language |
업데이트 생성 언어 (ko / en) |
ko |
Setup 로직:
config.json 읽기
├─ github_username 비어있음? → "GitHub 사용자명을 입력해주세요 (건너뛰려면 Enter)"
├─ jira_project_key 비어있음? → "기본 Jira 프로젝트 키를 입력해주세요 (예: PROJ, 없으면 Enter)"
├─ slack_channel 비어있음? → "스탠드업을 공유할 Slack 채널을 입력해주세요 (예: #daily-standup, 없으면 Enter)"
└─ 답변 수집 후 config.json에 저장 → 이후 자동 사용
모든 필드가 채워져 있으면 이 단계를 건너뜁니다.
Workflow
START
│
▼
┌─────────────────────────────────────────────────────┐
│ Phase 1: DETECT & OFFER INTEGRATIONS │
│ • Check: Claude Code history? gh CLI? jira CLI? │
│ • Claude Code → Pull yesterday's session digest │
│ → User selects relevant items by numbered list │
│ • GitHub/Jira → Ask user, pull if approved │
│ • Pull data NOW (before interview) │
├─────────────────────────────────────────────────────┤
│ Phase 2: INTERVIEW (with insights) │
│ • Show pulled data as context │
│ • Yesterday: "I see you merged PR #123, what else?" │
│ • Today: What will you work on? │
│ • Blockers: Anything blocking you? │
│ • Topics: Anything to discuss at end of meeting? │
├─────────────────────────────────────────────────────┤
│ Phase 3: GENERATE UPDATE │
│ • Combine interview answers + tool data │
│ • Format as clean Markdown │
│ • Present to user │
└─────────────────────────────────────────────────────┘
What ships with it
2 files 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.
- 8d ago First seen · 448 lines · 45 tokens per session scan A d6e27ab40864
daily-meeting-update is a skill published in the GitHub repository Dannykkh/skill-olympus (5 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 3,368 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
factory-close
Close out a Linear issue — move to Done, add a closing comment, and clean up the local branch/worktree.
factory-submit
Move the current branch's Linear issue to "In Review".
factory-setup-linear
Configure portable Linear workflow settings in .factory-kit/linear.json, migrating legacy .claude/linear.json settings when present.
factory-entry
Load a Linear issue into context and enter plan mode for a focused session.
factory-standup
Dev standup — open Linear tickets grouped by in-flight, top priority, and backlog.
implement-batch
Use when you want to implement the next batch of a plan. Handles module implementation, testing, and validation.