Borrowing it
Nothing to install: this file belongs to Shashank2577/hesoyam-for-claude-code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Shashank2577/hesoyam-for-claude-code/main/.claude/skills/daily-standup/SKILL.mdgit clone --depth 1 https://github.com/Shashank2577/hesoyam-for-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/shashank2577/hesoyam-for-claude-code/daily-standup)<a href="https://agentmods.dev/skills/shashank2577/hesoyam-for-claude-code/daily-standup"><img src="https://agentmods.dev/badge/skills/shashank2577/hesoyam-for-claude-code/daily-standup/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/shashank2577/hesoyam-for-claude-code/daily-standup"><img src="https://agentmods.dev/badge/skills/shashank2577/hesoyam-for-claude-code/daily-standup.svg" alt="Reviewed on agentmods" width="80" 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.00025 | $0.00401 |
| Opus 5.5 | $0.00010 | $0.00160 |
| Sonnet 5.5 | $0.00005 | $0.00080 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
daily-standup 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 2mo 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
$VAULT_PATH defaults to ~/Documents/obsidian-vault. Override by setting VAULT_PATH in your environment or passing --vault-path during install.
Generate a concise daily standup report by pulling from two sources:
Source 1: claude-mem (if available)
- Search for observations from the last 24 hours
- Extract: files modified, features worked on, bugs fixed, PRs created, tests written
- Group by project/feature
- If claude-mem MCP tools are unavailable, skip this source and note "claude-mem not available" in the output
Source 2: Obsidian daily note (if available)
- Check
$VAULT_PATH/00_Inbox/and$VAULT_PATH/01_Projects/for today's and yesterday's notes - Extract any manually captured context, blockers, or decisions
Output format:
## Standup — [date]
### Yesterday
- [Completed item 1 — with context]
- [Completed item 2 — with context]
### Today
- [Planned item 1 — based on in-progress work and open PRs]
- [Planned item 2 — based on vault project notes]
### Blockers
- [Any unresolved issues from yesterday's session]
- [Any dependencies or questions noted in vault]
Rules:
- Keep each item to one line. No paragraphs.
- Use past tense for yesterday, future tense for today.
- Only include actual work done — no filler like "reviewed emails" or "attended meetings" unless they produced code artifacts.
- If no blockers exist, write "None" — don't invent problems.
- If working on multiple projects, group by project with headers.
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.
- 2mo ago First seen · 44 lines · 25 tokens per session scan A 5166498fb04c
daily-standup is a skill published in the GitHub repository Shashank2577/hesoyam-for-claude-code (11 stars, last pushed 7mo ago), licensed MIT. It adds 25 tokens to every session and 401 once invoked, about $0.0001 per session on Opus 5.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.
daily-standup compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| daily-standupShashank2577/hesoyam-for-claude-code | Skill | 11 | 7mo ago | MIT | A | 25 | Claude Code |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |