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 GktuOktay/ai-skills --skill standupgit clone --depth 1 https://github.com/GktuOktay/ai-skillsWrote 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/gktuoktay/ai-skills/standup)<a href="https://agentmods.dev/skills/gktuoktay/ai-skills/standup"><img src="https://agentmods.dev/badge/skills/gktuoktay/ai-skills/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/gktuoktay/ai-skills/standup"><img src="https://agentmods.dev/badge/skills/gktuoktay/ai-skills/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.00048 | $0.00743 |
| Opus 5.5 | $0.00019 | $0.00297 |
| Sonnet 5.5 | $0.00010 | $0.00149 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
Daily Standup Generator 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 1mo 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daily Standup Generator Guidelines
This skill defines how to aggregate, filter, and format development progress into professional daily standup reports. The goal is to provide maximum visibility with minimal reading time.
1. Core Formatting (The 3 Pillars)
Every standup report must follow a strict, scannable format divided into three core sections:
Yesterday (Ne Yaptım?)
Focus on completed work and measurable progress.
- Use bullet points.
- Start with strong action verbs (e.g., Implemented, Fixed, Refactored, Reviewed).
- Include ticket/issue numbers or links where applicable.
Today (Ne Yapacağım?)
Focus on the immediate priorities for the current day.
- Be specific about the expected outcome (e.g., Finalize the API endpoint instead of Work on API).
- Mention any meetings or cross-team collaborations planned.
Blockers (Engeller)
Highlight anything preventing progress.
- Be clear about who or what you are waiting for.
- If there are no blockers, state: "None" or "No blockers." Do not omit the section.
2. Extracting Progress from Git Logs & Trackers
When automating this process using git logs or Jira/Linear tickets, apply the following filters:
- Filter Noise: Ignore trivial commits like "fix typo," "update readme," or merge commits unless they represent a significant milestone.
- Aggregate Commits: If there are 5 commits related to
#PROJ-123 Authentication, summarize them into one bullet point: "Completed backend integration for Authentication flow (#PROJ-123)." - Highlight PRs: Always mention Pull Requests that were opened, merged, or reviewed.
3. Keeping It Concise
Standup updates are not novels. They are designed for quick team alignment.
- Limit details: Avoid deep technical implementation details unless relevant to a blocker.
- Max 3-5 bullets: Per section (Yesterday/Today). If there is more, summarize the broader themes.
- Example:
- Too detailed: "Wrote a SQL query using inner joins to connect the users table with the orders table, handled edge cases for null values, and added indexing to improve the query execution time by 400ms."
- Concise: "Optimized user order history database queries, improving performance."
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.
- 1mo ago First seen · 69 lines · 48 tokens per session scan A 275845a76dd3
Daily Standup Generator is a skill published in the GitHub repository GktuOktay/ai-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 743 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
wayfinder
Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
to-spec
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
task
AI DevKit · Track dev-lifecycle / dev-debug progress on a durable task with the ai-devkit task CLI. Use to record phase, progress, next step, blockers, and validation evidence.
conductor-new-track
Create a new track with specification and phased implementation plan.
utility-pm-skill-iterate
Applies targeted improvements to an existing pm-skills skill based on feedback, validation reports, or convention changes. Reads current files, previews proposed changes, writes on confirmation, and suggests a version bump. Use when improving a skill after validation or feedback.
dev-retro
AI DevKit · Run an evidence-based retrospective on finished work (feature, session, incident) and turn friction into durable fixes, automation first. Use when users ask for a retro, lessons learned, post-mortem, or "what went wrong", or when another skill offers one after a feature or fix.