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 agentmods add commands/vvedantb/eva/standupgit clone --depth 1 https://github.com/vvedantb/evaWrote 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/vvedantb/eva/standup)<a href="https://agentmods.dev/commands/vvedantb/eva/standup"><img src="https://agentmods.dev/badge/commands/vvedantb/eva/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 | $0.00000 | $0.00327 |
| Opus 5 | $0.00000 | $0.00163 |
| Sonnet 5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
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 yesterday.
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
Review my git commits from the past workday and generate a standup summary.
Steps
- Determine the
--sincevalue: rundate +%uto get the day of week (1=Mon, 7=Sun). If today is Monday (1), use--since="last Friday 00:00". Otherwise use--since="yesterday 00:00". - Run
git log --author="$(git config user.name)" --since="<value from step 1>" --pretty=format:"%h %s" --no-mergesto get my commits. - If there are commits, run
git log --author="$(git config user.name)" --since="<value from step 1>" --no-merges --statto understand the scope of changes. - Group related commits together by feature/area (don't list every commit individually if they're related).
- Output a concise standup in this format:
## Standup — <today's date>
**Done:**
- <bullet point summarizing a feature/fix/task>
- <bullet point summarizing a feature/fix/task>
Rules
- Keep each bullet to one line, max two sentences.
- Group related commits into a single bullet rather than listing each commit separately.
- Focus on WHAT was accomplished, not HOW (no file names or technical details unless they add clarity).
- If no commits found, say "No commits in the last 24 hours."
- Do not include merge commits.
- Do not include commit hashes in the output.
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.
- yesterday First seen · 27 lines · 0 tokens per session scan A a9a236be8b13
standup is a command published in the GitHub repository vvedantb/eva (101 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 327 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-09-03.
Other commands, from other repositories
status
Generate a comprehensive project status report — active features, recent decisions, agent recommendations, and health assessment.
gsd:quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
backlog-git
Control de versiones para backlogs de proyectos.
company-repo
Gestionar el repositorio Company Savia: crear, conectar, estado, sincronizar. El repositorio compartido de la empresa para conocimiento, mensajería y estado.
contribute
Contribuir mejoras, ideas o correcciones al repositorio de pm-workspace en GitHub.
backlog-sync
Sync local backlog with external PM tools (Azure DevOps, Jira, GitHub Issues).