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-wrapgit 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-wrap)<a href="https://agentmods.dev/skills/sprintra-io/sprintra-mcp/sprintra-wrap"><img src="https://agentmods.dev/badge/skills/sprintra-io/sprintra-mcp/sprintra-wrap/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-wrap"><img src="https://agentmods.dev/badge/skills/sprintra-io/sprintra-mcp/sprintra-wrap.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.00043 | $0.00611 |
| Opus 5 | $0.00022 | $0.00305 |
| Sonnet 5 | $0.00009 | $0.00122 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
wrap 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 11d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wrap Up Session
Save the current coding session's context to Sprintra so the next session can resume seamlessly. This is the "save game" for development work.
Process
Step 1: Check Active Session
Call work_sessions(method: "get_active"). If no active session, skip to summary.
Step 2: Analyze What Happened
Look at:
- Git status: what files were changed (use
git diff --stat HEAD~5via Bash if needed) - Conversation context: what stories were worked on, what decisions were made
- Any stories that should be marked done
Step 3: Update Story Statuses
For any stories completed during this session:
stories(method: "update", story_id: "...", status: "done")
Add a comment to each completed story:
comments(method: "create", entity_type: "story", entity_id: "...", content: "Completed: [what was done, files changed, how tested]")
Step 4: Save Feature Context (if applicable)
If a feature was being worked on, save where you left off:
features(method: "save_context", feature_id: "...", where_left_off: "...", last_session_summary: "...", files_touched: [...])
Step 5: End Work Session
work_sessions(method: "end", summary: "...", files_changed: [...], stories_completed: [...], next_steps: "...")
Include:
- summary: 1-2 sentences of what was accomplished
- files_changed: key files modified (not every file — just the important ones)
- stories_completed: IDs of stories marked done
- next_steps: what to pick up next time (critical for session continuity)
Step 6: Git Sync (if commits were made)
git(method: "sync")
Then link commits to stories:
git(method: "link", story_id: "...", commit_hash: "...")
Step 7: Show Summary
## Session Wrapped ✓
Duration: [start time] → [now]
Stories completed: [list]
Files changed: [count]
Next steps: [what to do next time]
Context saved — next session will auto-resume.
Important
- This should take <30 seconds. Don't over-analyze — capture the essentials.
- If the user didn't work on any tracked stories, just end the session with a summary.
- Always include
next_steps— this is the most valuable field for session continuity. - Don't ask questions. Just gather, save, and confirm.
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.
- 11d ago First seen · 85 lines · 43 tokens per session scan A 4ccc30a80f2d
wrap is a skill published in the GitHub repository Sprintra-io/sprintra-mcp (3 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 611 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
help-flow
Help about Rosetta: explains capabilities and usage.
modernization-flow
Workflow for converting, modernizing, upgrading, or re-architecting code (e.g. C++→Java, monolith→microservices), etc.
external-lib-flow
Workflow for onboarding an external private library so AI can use it without source access.
coding-flow
Light coding workflow: features, fixes, refactors, unit tests, etc.; scales small to large.
adhoc-flow
Workflow for the rest of tasks: lightweight documentation, build, track, synchronize, etc.
coding-agents-prompting-flow
Workflow for authoring and adapting AI-agent prompts: skills, agents, workflows, rules, etc.