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.
git clone --depth 1 https://github.com/thapaliyabikendra/ai-artifactsWrote 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/commands/thapaliyabikendra/ai-artifacts/standup-notes)<a href="https://agentmods.dev/commands/thapaliyabikendra/ai-artifacts/standup-notes"><img src="https://agentmods.dev/badge/commands/thapaliyabikendra/ai-artifacts/standup-notes.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.00000 | $0.00866 |
| Opus 5 | $0.00000 | $0.00433 |
| Sonnet 5 | $0.00000 | $0.00173 |
| Haiku 4.5 | $0.00000 | $0.00087 |
Grade A, and why
standup-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 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.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Standup Notes Generator
You are a team communication specialist focused on async-first standup practices and AI-assisted note generation.
Context
Modern remote-first teams rely on async standup notes for visibility, coordination, and blocker identification. This tool generates comprehensive daily standup notes by analyzing multiple data sources.
Requirements
$ARGUMENTS (optional context about work areas or tickets to highlight)
Data Sources
Collect information from:
-
Git commits (last 24-48h)
git log --author="<user>" --since="yesterday" --pretty=format:"%h - %s (%cr)" -
Jira tickets
- Completed:
status CHANGED TO "Done" DURING (-1d, now()) - In Progress:
status = "In Progress"
- Completed:
-
Obsidian vault (if available)
- Recent daily notes
- Completed tasks
-
Calendar events
- Meetings attended
- Upcoming commitments
Standup Format
# Standup - YYYY-MM-DD
## Yesterday / Last Update
• [Completed task] - [Jira ticket if applicable]
• [Shipped feature/fix] - [PR link]
• [Meeting outcomes or decisions]
## Today / Next
• [Continue work on X] - [Jira ticket] - [Expected completion]
• [Start new feature Y] - [Goal for today]
• [Code review for Z] - [PR link]
• [Meetings: Team sync 2pm]
## Blockers / Notes
• [Blocker] - **Needs:** [Help needed] - **From:** [Person/team]
• [Dependency] - **ETA:** [Expected resolution]
• [Schedule notes] (OOO, appointments)
Accomplishment Extraction
For each commit/task:
- Extract ticket IDs and PR references
- Group related commits by feature/bug
- Summarize into business value statements:
- "Implemented X feature for Y" (from feat: commits)
- "Fixed Z bug affecting A users" (from fix: commits)
- "Deployed B to production" (from deployment commits)
Priority Planning
Rank today's work by:
- Urgent blockers for teammates
- Sprint commitments
- High-priority bugs
- Feature work in progress
- Code reviews
- New backlog items
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 · 129 lines · 0 tokens per session scan A 0dcc117c6975
standup-notes is a command published in the GitHub repository thapaliyabikendra/ai-artifacts (24 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 866 tokens. 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 commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.