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 codecast-sh/codecast --skill cast-standupgit clone --depth 1 https://github.com/codecast-sh/codecastWrote 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/codecast-sh/codecast/cast-standup)<a href="https://agentmods.dev/skills/codecast-sh/codecast/cast-standup"><img src="https://agentmods.dev/badge/skills/codecast-sh/codecast/cast-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/codecast-sh/codecast/cast-standup"><img src="https://agentmods.dev/badge/skills/codecast-sh/codecast/cast-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.00051 | $0.00524 |
| Opus 5.5 | $0.00020 | $0.00210 |
| Sonnet 5.5 | $0.00010 | $0.00105 |
| Haiku 4.5 | $0.00005 | $0.00052 |
Grade A, and why
cast-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.
What it actually says
Standup tools read one person's local logs. This reads what the whole team's sessions did, plus the systems around them.
Gather, in parallel
Default window is one day; --mine or -m <member> narrows the author.
cast feed -s <window> -n 40 [--mine | -m <member>] # sessions: titles, edits, last turns
cast diff --today # or --week: files and commits across sessions
cast task ls -s done -a # closed work; cast task ls -s in_progress for what is open
cast task ready # unclaimed work
cast pr ls # open pull requests and their state
cast decisions --project . # decisions recorded in the window
cast calls -n 5 # then cast call <id> for the summary and action items
cast chat channels # unread counts; cast chat read --channel <id> for the busy ones
git log --since="<window> ago" --oneline
Read a session (cast read <id>) only when the feed line does not say what
it delivered or why it stopped.
Write
Five sections, each a short list, each item ending with the session, task or pull request short id so it renders as a live reference:
- Done: what shipped, verified how.
- In progress: what is moving and who acts next.
- Blocked: what waits on a human, and which human.
- Decisions: what was decided and the reason, one line each.
- Next: what is queued, from
cast task readyand the pinned states.
Lead each item with the outcome, not the activity. A session that ran for four hours and delivered nothing goes under Blocked or is omitted, not under Done. Omit any section with nothing in it.
Post
If asked to post, cast chat send --channel <id> - with the digest on stdin,
or cast publish it as a page and put the link in the reply. Otherwise reply
with the digest and stop.
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 · 49 lines · 51 tokens per session scan A 63b9d144fe22
cast-standup is a skill published in the GitHub repository codecast-sh/codecast (40 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 524 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-09-15.
Other skills, from other repositories
to-tickets
Slice a spec or a ticket into tracer-bullet tickets with blocking edges, saved to .specs/tickets/ .md.
to-spec
Turn the settled conversation into a spec (PRD) at .specs/specs/ .md.
register-project
Register an existing project in memory. Use when starting work on a new repo or when a project needs its own context file. Triggers on: 'register project', 'add project to memory', 'track this project', 'create project file'.
idea-vault
Cross-project idea capture and review. A notebook-with-reminders that logs the user's ideas, plans, and checklists across every project, in one plain-markdown file. Use this skill whenever the conversation contains a new idea, plan, or intention the user might want to save for later, and whenever a project milestone…
status
Show project status dashboard across registered repositories.
github-project-management
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.