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 AgiFlow/ai-plugin --skill daily-standupgit clone --depth 1 https://github.com/AgiFlow/ai-pluginWrote 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/agiflow/ai-plugin/daily-standup)<a href="https://agentmods.dev/skills/agiflow/ai-plugin/daily-standup"><img src="https://agentmods.dev/badge/skills/agiflow/ai-plugin/daily-standup.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.00048 | $0.00370 |
| Opus 5 | $0.00024 | $0.00185 |
| Sonnet 5 | $0.00010 | $0.00074 |
| Haiku 4.5 | $0.00005 | $0.00037 |
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 7d 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.
This is a copy
100% identical to daily-standup — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Agiflow Daily Standup
Give a brief, evidence-based project pulse. Do not modify workspace data.
Workflow
- Call
get_current_scopeand resolve the requested project when needed. - Call
list_active_tasks_by_orgfor current active work. - Call
list_work_unitsfor active and blocked work units. - Call
get_project_detailwhen the summary is project-specific. - Call
list_membersto resolve assignee context. - Call
get_task,get_work_unit_progress, orlist_task_commentsonly when needed to confirm progress or a blocker. - Summarize:
- Done or moved to Review since the latest available update
- Current work in progress
- Blocked or stalled items
- Highest-priority next actions
Priority Logic
- Resolve blockers that prevent other work.
- Finish existing work in progress before starting more work.
- Select the highest-priority ready item.
- Recommend refinement when a task is not ready.
Output Format
Use short sections titled Done, In Progress, Blocked, and Next Up. Include task or work-unit identifiers when available. State clearly when no recent changes or blockers are found.
Guardrails
- Remain read-only. Do not call mutation tools.
- Do not claim an item changed recently unless the returned data supports that conclusion.
- Distinguish confirmed blockers from possible signs of stalled work.
- Keep the summary scannable and end with one clear recommendation.
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.
- 7d ago First seen · 41 lines · 48 tokens per session scan A 8ee379dd9960
daily-standup is a skill published in the GitHub repository AgiFlow/ai-plugin (3 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 370 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to daily-standup, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.