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 joris887/exosuit --skill sprint-startgit clone --depth 1 https://github.com/joris887/exosuitWrote 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/joris887/exosuit/sprint-start)<a href="https://agentmods.dev/skills/joris887/exosuit/sprint-start"><img src="https://agentmods.dev/badge/skills/joris887/exosuit/sprint-start.svg" alt="Measured on agentmods" 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.00033 | $0.02591 |
| Opus 5 | $0.00016 | $0.01295 |
| Sonnet 5 | $0.00007 | $0.00518 |
| Haiku 4.5 | $0.00003 | $0.00259 |
Grade A, and why
sprint-start 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 8d 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sprint-start
Skill metrics: Emit a start event to the activity log:
echo "{\"type\":\"skill\",\"event\":\"start\",\"skill\":\"sprint-start\",\"ts\":\"$(date -u +%Y-%m-%dT%H:%M:%SZ)\"}" >> docs/sessions/.activity-log.jsonl
Starting a new sprint.
Profile-Adaptive Behavior
Read the **Profile:** line from CLAUDE.md to determine the active project profile.
1. Pre-flight Checks
Verify the workspace is ready for new work:
1a. Check for open PRs
gh pr list --author @me --state open
If open PRs exist:
- Check if any are approved → merge them:
gh pr merge --squash --delete-branch - If awaiting review → inform user and ask whether to proceed or wait
1b. Verify clean working tree
git status
If uncommitted changes exist:
- Warn user — they must commit, stash, or discard before proceeding
- Do NOT proceed with dirty working tree
1c. Ensure on default branch and up to date
Read the Default branch from CLAUDE.md's Git Workflow section. If not set, detect it at runtime:
# Read from CLAUDE.md first, fall back to detection
DEFAULT_BRANCH=$(grep -oP '^\- \*\*Default branch:\*\* \K\S+' CLAUDE.md 2>/dev/null)
if [ -z "$DEFAULT_BRANCH" ]; then
DEFAULT_BRANCH=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@')
fi
if [ -z "$DEFAULT_BRANCH" ]; then
for branch in main master develop; do
if git show-ref --verify --quiet "refs/heads/$branch"; then
DEFAULT_BRANCH="$branch"
break
fi
done
fi
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.
- 8d ago First seen · 275 lines · 33 tokens per session scan A 13d883f6b67a
sprint-start is a skill published in the GitHub repository joris887/exosuit (4 stars, last pushed 18d ago), licensed MIT. It adds 33 tokens to every session and 2,591 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
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
orchestrator-lanes
A file-based project-management playbook for a specific Claude Code development orchestrator. It organizes work into lanes, plans, dependency steps, validation phases, and shipping stages.
project-life
A system for keeping project ideas, tasks, plans, progress, decisions, and lessons in one place. A monorepo-style project workflow is implied, but the input does not define the storage format in full.
lane-contract
A file-based task contract system for describing coding tasks in YAML, including which files a task owns and how it must be checked.
plan-pipeline
Orchestrates the complete planning pipeline: product direction (ceo-review) -> architecture (eng-review) -> implementation plan (start) -> validation (validate) -> execution (execute). Run stages individually or let the orchestrator coordinate the full flow.
seo-project-life
A guide to the files, commands, stages, and working process of an SEO project. SEO, or search-engine optimization, is the work of improving a site's visibility in search results.