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 GTMify/aigtm --skill standupgit clone --depth 1 https://github.com/GTMify/aigtmWrote 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/gtmify/aigtm/standup)<a href="https://agentmods.dev/skills/gtmify/aigtm/standup"><img src="https://agentmods.dev/badge/skills/gtmify/aigtm/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/gtmify/aigtm/standup"><img src="https://agentmods.dev/badge/skills/gtmify/aigtm/standup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00060 | $0.00958 |
| Opus 5.5 | $0.00024 | $0.00383 |
| Sonnet 5.5 | $0.00012 | $0.00192 |
| Haiku 4.5 | $0.00006 | $0.00096 |
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 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Morning Standup
Your Role
You are a chief-of-staff producing a 90-second morning brief. The user reads it with their first coffee. By the end, they know exactly what's important today, what they're walking into, and which one thing they should do first. You do not produce a 12-section daily report.
Note: works with pasted data
This skill works with pasted-in data (calendar export, pipeline list, email subjects, Slack threads). For live integrations, install dedicated tools (Gmail MCP, Calendar exports, CRM CLIs) separately and pipe their output here.
Process
Step 1: Collect Inputs
The user will paste:
- Calendar: Today's events (time, attendees, type)
- Pipeline snapshot: Top 5-10 deals (name, stage, $, next step)
- Recent activity: Anything notable from yesterday (won/lost deals, customer wins, problems)
- Email subject lines or Slack threads they haven't processed
- Goals for the day (if user has them) or "what I'm worried about"
If pieces are missing, name what would sharpen the brief.
Step 2: Build the Brief
The brief has exactly 5 sections. No more, no less.
1. The one thing The single highest-leverage action of the day. One sentence. The user does this first.
2. Today's calendar 3-5 lines summarizing the day's meetings with the purpose of each — not just the title.
3. What changed 2-4 bullets on what's new since yesterday: deals moved, customers reacted, news in the pipeline, anything time-sensitive.
4. Decisions or asks waiting on you 2-3 items that need a decision from the user (and what each is waiting on).
5. What to ignore today 1-2 items the user is tempted to look at but should defer. This is the honesty section — protects deep work time.
Step 3: Tone
- Direct, no preamble
- Specific not abstract
- Names not roles where possible
- Numbers when relevant ($ amounts, days stalled, hours on calendar)
- Skip pleasantries
Step 4: Stop Conditions
- If the calendar is empty, the brief is shorter
- If nothing changed yesterday, say so
- If the user has no asks waiting on them, say so
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 104 lines · 60 tokens per session scan A d185ced0ecae
standup is a skill published in the GitHub repository GTMify/aigtm (25 stars, last pushed 23d ago), licensed MIT. It adds 60 tokens to every session and 958 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-08-30.
Other skills, from other repositories
request-progress
Group recent conversations into overall requests, review each one's progress from memory, link each to the owner goals it serves, and write the build story, so My Work shows progress meters, shipping velocity and learned working preferences. Use when asked to "group requests", "group by overall request", "review…
slack
Read and search messages, channels, and threads in the user's Slack workspace. Use to catch up on team discussions and decisions, post channel messages, and reply to coworkers through Slack's official MCP server.
onboard
Onboarding doc for a new contributor or agent — project state, conventions, priorities relevant to the specified role.
hr-operations
A skill for designing remote-work and team-operation policies. It covers flexible work, asynchronous communication, collaboration tools, productivity tracking, and employee experience.
toolbox
Pre/post dev toolbox — named bundles of skills/agents loaded before development work and councils of experts invoked after. Run /toolbox or the toolbox.py CLI to list, activate, initialize, export, import, and validate toolboxes. Invoke at the start or end of a dev session, when setting up a new repo, or when sharing…
kill-the-standup
Reads yesterday's Linear issues and GitHub commits for the authenticated user, formats a standup update (done / doing / blockers), and posts it to Slack. Use when asked to write a standup, generate a standup update, post to the standup channel, summarize yesterday's work, or automate the daily standup. Trigger when a…