A coordinated improvement session in which multiple agents research problems, plan changes, build improvements, and test the results.

It helps run research-only, build-only, or full improvement sessions focused on areas such as gates, skills, or memory.

It provides a repeatable process for finding and addressing several framework weaknesses instead of tackling improvements ad hoc.

sprint — Skill for Claude Code by OZmasterAI/Torus-Framework

Install

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.

Any agent

npx skills add OZmasterAI/Torus-Framework --skill sprint

Clone the repo

git clone --depth 1 https://github.com/OZmasterAI/Torus-Framework

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ozmasterai/torus-framework/sprint/github.svg)](https://agentmods.dev/skills/ozmasterai/torus-framework/sprint)

Your own site

<a href="https://agentmods.dev/skills/ozmasterai/torus-framework/sprint"><img src="https://agentmods.dev/badge/skills/ozmasterai/torus-framework/sprint/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ozmasterai/torus-framework/sprint"><img src="https://agentmods.dev/badge/skills/ozmasterai/torus-framework/sprint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 522 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00000	$0.00522
Opus 5.5	$0.00000	$0.00209
Sonnet 5.5	$0.00000	$0.00104
Haiku 4.5	$0.00000	$0.00052

Measured 1mo ago against content hash db721948cce6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sprint 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.

dormant/skills/self-improve/sprint/SKILL.md · 61 lines

How it starts

The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/sprint — Multi-Agent Self-Improvement Sprint

When to use

When user says "sprint", "self-improve sprint", "autonomous improvement", "launch improvement swarm", or wants to run a coordinated multi-agent improvement session.

Commands

/sprint — Full sprint with research + build + test phases
/sprint research — Research-only phase (no code changes)
/sprint build — Build-only phase (assumes research done)
/sprint $ARGUMENTS — Focus on specific area (e.g., "gates", "skills", "memory")

Flow

Phase 1: ASSESS (2 min)

Run /benchmark --quick to capture baseline metrics
Read LIVE_STATE.json for current state
Search memory for previous sprint results
Identify top 5 improvement opportunities

Phase 2: RESEARCH (5 min)

Launch research swarm (3-5 haiku agents in parallel):

Agent 1: Search GitHub for Claude Code frameworks
Agent 2: Search for self-improving agent patterns
Agent 3: Search for specific area improvements (from $ARGUMENTS)
Collect results, save to memory

Phase 3: PLAN (2 min)

Synthesize research findings
Create prioritized task list using TaskCreate
Score each task: Impact (40%) + Effort (30%) + Risk (20%) + Novelty (10%)
Select top 5-7 tasks for implementation

Phase 4: BUILD (10 min)

Launch builder team (3-5 sonnet agents):

Create agent team with TeamCreate
Assign tasks to team members
Monitor progress via TaskList
Handle blocking issues

Phase 5: VERIFY (3 min)

Run full test suite
Compare metrics against Phase 1 baseline
Fix any regressions

Phase 6: REPORT (1 min)

Generate sprint report with /report sprint
Save comprehensive results to memory
Update LIVE_STATE.json and ARCHITECTURE.md
Git commit all changes

Rules

NEVER exceed 7 concurrent agents (resource limit)
Research agents use haiku model, builders use sonnet
Always capture baseline BEFORE making changes
Stop after 2 consecutive test regressions (circuit breaker)
Save all research and decisions to memory
Maximum sprint duration: 25 minutes
Update LIVE_STATE.json at each phase transition

Read the full file on GitHub · 61 lines

Changes

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 · 61 lines · 0 tokens per session scan A db721948cce6

Subscribe to this mod's changes

sprint is a skill published in the GitHub repository OZmasterAI/Torus-Framework (5 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 522 tokens. 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.

Planning Project management

story-readiness

Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.

Donchitos/Claude-Code-Game-Studios · 35 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens

handle-linkedin-connection-request-signal

Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…

swan-gtm/gtm-skills · 160 tokens