Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/speedscale/speedy-templatenpx agentmods add skills/speedscale/speedy-template/speedscale-changeWrote 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/speedscale/speedy-template/speedscale-change)<a href="https://agentmods.dev/skills/speedscale/speedy-template/speedscale-change"><img src="https://agentmods.dev/badge/skills/speedscale/speedy-template/speedscale-change/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/speedscale/speedy-template/speedscale-change"><img src="https://agentmods.dev/badge/skills/speedscale/speedy-template/speedscale-change.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.00087 | $0.02867 |
| Opus 5.5 | $0.00035 | $0.01147 |
| Sonnet 5.5 | $0.00017 | $0.00573 |
| Haiku 4.5 | $0.00009 | $0.00287 |
Grade A, and why
speedscale-change 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 2mo 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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Speedscale Change
Customization: This skill is named after the Speedscale project — rename it to fit yours. Replace
SPDwith your Jira project prefix throughout.
Orchestrate end-to-end implementation of Jira tickets by combining the jira-tickets, gitflow, and glab-speedscale skills.
You are the orchestrating manager. Delegate research, investigation, implementation, and review to sub-agents liberally. Preserve your context for high-level orchestration.
What are sub-agents? OpenClaw can spawn isolated background sessions that run independently and report back when done. The orchestrator (you) delegates work like code exploration, implementation, and review to these sub-agents, keeping your own context focused on the big picture. Sub-agents have full access to the filesystem and tools but run in their own session.
Prerequisites
Load these skills as needed during the workflow:
- jira-tickets — ticket operations (view, transition, comment, assign)
- gitflow — worktree creation, branching, git operations
- glab-speedscale — MR creation, pipeline checks, comment responses
Repo Location
The repo lives at the path configured in TOOLS.md. All worktrees are created as siblings with a date prefix for ordering:
- Branch name:
SPD-XXXX-short-description(NOfeature/prefix — branches are shared) - Worktree directory:
../YYYY-MM-DD_SPD-XXXX-short-description(relative to main repo)
Thoughts Directory
Every worktree gets a thoughts/ directory at its root. This is your audit trail — if someone visits the worktree after you're done (success or failure), they should be able to reconstruct your process from these files.
Markdown naming: YYYY-MM-DD_HH-MM-SS_description.md (24h format, kebab-case description)
- Example:
2026-02-13_14-30-00_proxymock-flag-handling-analysis.md
Scripts in thoughts/ can use normal naming.
Write artifacts generously. Beyond the required analysis and abort files, also write:
- Investigation findings and dead ends explored
- Design decisions and alternatives considered
- Test strategies and results
- Review feedback received and how you responded
- Any debugging notes or hypotheses tested
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.
- 2mo ago First seen · 246 lines · 87 tokens per session scan A 9789e344f91f
speedscale-change is a skill published in the GitHub repository speedscale/speedy-template (5 stars, last pushed 8mo ago), licensed MIT. It adds 87 tokens to every session and 2,867 once invoked, about $0.0003 per session on Opus 5.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
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…