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 gyoung55/cowork-session-skills --skill standupgit clone --depth 1 https://github.com/gyoung55/cowork-session-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/gyoung55/cowork-session-skills/standup)<a href="https://agentmods.dev/skills/gyoung55/cowork-session-skills/standup"><img src="https://agentmods.dev/badge/skills/gyoung55/cowork-session-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/gyoung55/cowork-session-skills/standup"><img src="https://agentmods.dev/badge/skills/gyoung55/cowork-session-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.00078 | $0.01375 |
| Opus 5 | $0.00039 | $0.00687 |
| Sonnet 5 | $0.00016 | $0.00275 |
| Haiku 4.5 | $0.00008 | $0.00137 |
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 13d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Standup
This skill builds full working memory at the start of every session. It eliminates the ramp-up period where you operate without context and the user has to manually re-feed information from previous sessions. Do not start substantive work until this protocol completes and the user confirms.
Why This Exists
Persistent projects accumulate decisions, state changes, and context across many sessions. Without a structured standup, early-session work risks operating on stale assumptions, missing recent decisions, or duplicating effort. The /conclude skill captures everything at session end; this skill ingests it at session start. They are a matched pair.
Execution Steps
Run these steps sequentially. Do not skip steps. Do not start working on anything until the final step is complete and the user confirms.
Step 1: Core Reads
Read all state files completely. Do not skim. Do not rely on memory from prior sessions — read the current files every time.
-
STATUS.md(project root) — Current project state, priorities, open decisions. This is the entry point and quick-glance overview of where things stand. -
Latest file in
session-logs/(sort by filename date, most recent first) — What happened last session: files modified, decisions made, open threads, state at session end. If the log contains a<!-- session-state ... -->block, parse it for structured metadata (open thread count, pending handoffs, priority changes, suggested next focus).
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.
- 13d ago First seen · 105 lines · 78 tokens per session scan A ed4feec44881
standup is a skill published in the GitHub repository gyoung55/cowork-session-skills (5 stars, last pushed 5mo ago), licensed MIT. It adds 78 tokens to every session and 1,375 once invoked, about $0.0004 per session on Opus 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
rb:compound
Capturing a solved Ruby/Rails/Grape problem as reusable knowledge. YAML solution doc. Triggers: "compound this", "save this solution", "capture this fix".
ax-cpp-agent-memory-skills
Use when writing C++ code with axllm for agent memory, recall callbacks, dynamic skill discovery, loaded-skill state, and used-skill tracking.
new
Create a new project to start development quickly.
wax
Swift framework guidance for Wax on-device memory/RAG. Use when writing Swift code with the public Memory facade, experimental PhotoMemory / VideoMemory, BuiltInMultimodalEmbeddings, embedding providers, retrieval modes, or hybrid search. For agent operators using the Wax MCP server tools, use the separate wax-mcp…
rspec-conventions
Rootstrap RSpec conventions. Use when writing, reviewing, or editing RSpec test files (spec//spec.rb, spec/railshelper.rb, spec/spechelper.rb, spec/support//.rb) or factories. Covers describe/context structure, let/subject, matchers, factories, mocking/stubbing, shared examples, and spec types (model, request…
ruby-patterns
Ruby/Rails: blocks, metaprogramming, ActiveRecord, Sidekiq, RSpec, Sorbet, Hanami. Triggers: Ruby, Rails, ActiveRecord, Sidekiq, RSpec, Gemfile, bundler, Hanami, Sorbet.