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-capturegit 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-capture)<a href="https://agentmods.dev/skills/sprintra-io/sprintra-mcp/sprintra-capture"><img src="https://agentmods.dev/badge/skills/sprintra-io/sprintra-mcp/sprintra-capture/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-capture"><img src="https://agentmods.dev/badge/skills/sprintra-io/sprintra-mcp/sprintra-capture.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.00048 | $0.00862 |
| Opus 5 | $0.00024 | $0.00431 |
| Sonnet 5 | $0.00010 | $0.00172 |
| Haiku 4.5 | $0.00005 | $0.00086 |
Grade A, and why
capture 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Capture Feature into Sprintra
You are capturing a product feature into Sprintra project management. Your job is to have a SHORT conversation (2-3 exchanges max) to understand what the user wants, then create well-structured artifacts via MCP tools. Do NOT over-interview — developers hate long Q&A. Get enough to create quality artifacts, infer the rest.
Input
The user described: $ARGUMENTS
Process
Step 1: Quick Clarification (1 exchange only)
If the description is clear enough to act on, skip to Step 2. Only ask if genuinely ambiguous. When you do ask, batch all questions into ONE message:
- What's the priority? (critical/high/medium/low) — infer from context if possible
- Any technical constraints or preferences?
- Target sprint or just backlog?
If the user gave enough context already, say "Got it, let me capture this" and proceed.
Step 2: Create the Feature
Call the features MCP tool:
features(method: "create", title: "...", description: "...", priority: "...", acceptance_criteria: [...])
Rules:
- Title: Short, action-oriented (e.g., "User Authentication System" not "Auth")
- Description: 2-3 sentences explaining the WHY and WHAT
- Priority: Infer from conversation tone — "need this ASAP" = critical, "would be nice" = low
- Acceptance criteria: 3-5 testable criteria derived from the conversation. Use "Given/When/Then" or simple "User can..." format
- Inferred fields: List any fields you inferred (not explicitly stated) in the
inferred_fieldsarray
Step 3: Break into Stories
For each distinct piece of work, call:
stories(method: "create", feature_id: "...", title: "...", type: "story|task|bug", story_points: N, description: "...", acceptance_criteria: [...])
Rules:
- Each story should be 2-4 hours of work (1-3 story points)
- Use types:
story(user-facing),task(technical),bug(fix),chore(maintenance) - Story points: 1 (trivial), 2 (small), 3 (medium), 5 (large), 8 (needs breakdown)
- If a story is 8+ points, break it further
- Include 2-3 acceptance criteria per story
- Order stories logically (foundation first, then features, then polish)
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 · 81 lines · 48 tokens per session scan A d6aad36d12c0
capture is a skill published in the GitHub repository Sprintra-io/sprintra-mcp (3 stars, last pushed 2mo ago), licensed MIT. It adds 48 tokens to every session and 862 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.