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 agentmods add skills/speedscale/speedy-template/speedscale-changenpx skills add speedscale/speedy-template --skill speedscale-changegit clone --depth 1 https://github.com/speedscale/speedy-templateWrote 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.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 | $0.00087 | $0.02867 |
| Opus 5 | $0.00044 | $0.01434 |
| Sonnet 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 4d 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.
- 4d 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 6mo ago), licensed MIT. It adds 87 tokens to every session and 2,867 once invoked, about $0.0004 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
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…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
loop
Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…
subagent-delegation
Canonical protocol for delegating GSD work to native Antigravity subagents — when to delegate, how to invoke, workspace isolation modes, and the inline fallback for older IDE versions.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.