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 Sprintra-io/sprintra-mcp --skill sprintra-standupgit clone --depth 1 https://github.com/Sprintra-io/sprintra-mcpWrote 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/sprintra-io/sprintra-mcp/sprintra-standup)<a href="https://agentmods.dev/skills/sprintra-io/sprintra-mcp/sprintra-standup"><img src="https://agentmods.dev/badge/skills/sprintra-io/sprintra-mcp/sprintra-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/sprintra-io/sprintra-mcp/sprintra-standup"><img src="https://agentmods.dev/badge/skills/sprintra-io/sprintra-mcp/sprintra-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.00044 | $0.00452 |
| Opus 5 | $0.00022 | $0.00226 |
| Sonnet 5 | $0.00009 | $0.00090 |
| Haiku 4.5 | $0.00004 | $0.00045 |
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 12d 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 Report
Generate a concise standup report by reading Sprintra data. No user input needed — just gather and summarize.
Process
Step 1: Gather Data (all in parallel if possible)
- Recent work sessions:
work_sessions(method: "list")— get last 1-2 sessions - Current sprint:
sprints(method: "get_current")— sprint progress - Recent activity:
work_sessions(method: "list_activity", limit: 20)— what changed recently - AI recommendation:
ai(method: "get_next_work")— what to work on next
Step 2: Format the Report
## Standup — [today's date]
### Done (since last session)
- [story title] — [status change] ([feature name])
- [what was accomplished in last work session]
- [commits made]
### In Progress
- [story title] — [current status] ([feature name])
- [what's being worked on]
### Next Up
- [AI recommended next story] — [why this one]
- [any blocked items]
### Sprint Progress
[sprint name]: [done]/[total] stories ([percentage]%)
[progress bar visualization]
Step 3: Flag Issues
If you notice:
- Stories stuck in "in_progress" for multiple sessions → flag as potentially blocked
- Sprint at risk (>50% time elapsed, <30% stories done) → flag
- No work session ended properly → remind about
/wrap
Important
- Keep it SHORT — developers scan standups, they don't read essays
- Use bullet points, not paragraphs
- Include the sprint progress bar — it's the most glanced-at element
- If no recent work sessions exist, say "No recent sessions found. Start one with
work_sessions(method: 'start')"
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.
- 12d ago First seen · 55 lines · 44 tokens per session scan A 1943399e2d0f
standup is a skill published in the GitHub repository Sprintra-io/sprintra-mcp (3 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 452 once invoked, about $0.0002 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-31.
Other skills, from other repositories
init-workspace-flow
Workflow for initializing or upgrading a workspace: context, discovery, documentation, etc.
arrange-workspace-flow
Workflow for arranging a workspace: layout, reference source code, business/technical context, ecosystem setup.
testgen-flow
Workflow for generating test cases from requirements (Issue Tracker / Wiki sources), exporting to a Test Management System, etc.
backlog
To validate story readiness for a sprint or to break work into a human WBS.
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.