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 tobihagemann/turbo --skill stagegit clone --depth 1 https://github.com/tobihagemann/turboWrote 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/tobihagemann/turbo/stage)<a href="https://agentmods.dev/skills/tobihagemann/turbo/stage"><img src="https://agentmods.dev/badge/skills/tobihagemann/turbo/stage/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/tobihagemann/turbo/stage"><img src="https://agentmods.dev/badge/skills/tobihagemann/turbo/stage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00039 | $0.00237 |
| Opus 5 | $0.00019 | $0.00118 |
| Sonnet 5 | $0.00008 | $0.00047 |
| Haiku 4.5 | $0.00004 | $0.00024 |
Grade A, and why
stage 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 6d 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
Stage Changes
Stage implementation changes with precise file selection.
Step 1: Identify Changes
Run git status to see all modified, added, and deleted files.
Step 2: Stage Files
Stage only the files relevant to the current task:
git add <file1> <file2> ...
- Do not use
git add -A,git add ., orgit add -u— all three sweep in unrelated changes - If a file contains both relevant and unrelated changes, use
git add -p <file>to stage only the relevant hunks - Never stage files containing secrets (
.env, credentials, API keys). Warn if detected.
Step 3: Verify
Run git status and git diff --cached to verify the staging area contains exactly the intended changes.
Then use the TaskList tool and proceed to any remaining task.
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.
- 6d ago First seen · 31 lines · 39 tokens per session scan A 7c36ea417195
stage is a skill published in the GitHub repository tobihagemann/turbo (402 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 237 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-09-03.
Other skills, from other repositories
git-pushing
Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.
ape-commit
Defines how to write and format git commit messages. Use this skill whenever the user asks you to write, draft, suggest, or format a git commit message, summarize changes into a commit, or help stage and describe code changes. Trigger even for casual requests like "write me a commit for this" or "what should my commit…
changelog
Use when writing a changelog or release notes. Covers what belongs in one, writing for users rather than for git, semantic versioning, and documenting breaking changes so nobody is surprised.
git-workflow
Use for branching, committing, history repair, and release hygiene. Covers atomic commits, rebase versus merge, bisect, reflog recovery, and undoing mistakes safely.
git
Granular git operations with conventional commits - stage, commit, push, PR, merge. Auto-splits commits by type/scope, blocks on secrets, delegates verbose work to git-manager subagent. GitHub CLI conventions: --body-file for PR bodies, treat gh pr checks exit 8 (pending) as retry not failure, guard run-id assignment…
optimize-loop
Autonomous metric-optimization loop - run N bounded iterations against a mechanical metric, commit each attempt, auto keep/discard on the number, revert regressions. Use to improve a measurable metric: test coverage, bundle size, lint/type-error count, p95 latency, LOC. Triggers: 'drive coverage up', 'reduce bundle…