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.
git clone --depth 1 https://github.com/lindoelio/spec-driven-steroidsWrote 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/commands/lindoelio/spec-driven-steroids/release)<a href="https://agentmods.dev/commands/lindoelio/spec-driven-steroids/release"><img src="https://agentmods.dev/badge/commands/lindoelio/spec-driven-steroids/release/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/commands/lindoelio/spec-driven-steroids/release"><img src="https://agentmods.dev/badge/commands/lindoelio/spec-driven-steroids/release.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.00017 | $0.01209 |
| Opus 5.5 | $0.00007 | $0.00484 |
| Sonnet 5.5 | $0.00003 | $0.00242 |
| Haiku 4.5 | $0.00002 | $0.00121 |
Grade A, and why
release 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 today.
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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release this repository using the established spec-driven-steroids publication flow.
User request / target version:
{{args}}
Goal
Prepare the requested package version, commit the release, deliver it to main, create the matching vX.Y.Z tag on the verified commit, and push that tag so .github/workflows/publish.yml publishes to npm automatically.
Do not run npm publish or pnpm publish manually. Publication is done by GitHub Actions after the tag push.
Follow CONTRIBUTING.md#maintainer-delivery. For the sole maintainer's authorized work, deliver directly to main using the owner's permitted admin bypass; do not introduce PR, code-owner, merge, or repeated release-approval gates. Preserve all validation, planning approvals, and safety permissions. This repository policy is not a rule to install into other projects.
Required Inputs
- Resolve the target version from the request, approved release plan, existing release preparation, or pending Changesets.
- Ask one short clarification only if those sources do not determine the version unambiguously. Do not ask for release authorization again when it is already part of the approved scope.
Successful Release Process
-
Inspect repository state.
- Run
git status. - Run
git diff --stat. - Run
git log --oneline -10. - Confirm the current branch and upstream state.
- Confirm the authenticated GitHub actor and permissions under the maintainer-delivery policy.
- Never revert or overwrite unrelated user changes.
- Run
-
Commit feature changes first, if any are present.
- Inspect the changed files enough to write an accurate commit message.
- Ensure user-facing platform additions are documented in the READMEs and later in the changelog.
- Stage the intended non-release files with
git add. - Commit them with a concise conventional message, for example
feat: add Cline platform support.
-
Create a Changesets entry for the target version.
- Read
packages/cli/package.jsonto determine the current version. - If the target version and changelog are already prepared, verify them and reuse that release commit; do not bump again or create a duplicate changeset.
- Choose the bump type needed to reach the target version:
patch,minor, ormajor. - Add
.changeset/release-X-Y-Z.mdwith this shape:
- Read
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.
- today First seen · 96 lines · 17 tokens per session scan A d4201ebdbc27
release is a command published in the GitHub repository lindoelio/spec-driven-steroids (54 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 1,209 once invoked, about $0.0001 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-10-25.
Other commands, from other repositories
sddp-implement
Command description: Implement the current feature tasks. Argument hint: [optional: phase or task to start from] Command category: feature-delivery Prerequisites: spec, plan, tasks, checklists:complete-if-present.
ship
Deploy feature through automated staging validation to production with rollback testing.
sddp-prd
Command description: Create or refine the canonical product document. Argument hint: [rough product idea, users, domain, or market opportunity] Command category: project-bootstrap Prerequisites: none.
sddp-specify
Command description: Create a feature specification from a feature description. Argument hint: [feature description] Command category: feature-delivery Prerequisites: project-instructions.
sddp-amend
Command description: Propagate a bootstrap change across canonical project artifacts and the project plan. Argument hint: [project-level change to propagate across bootstrap artifacts] Command category: project-bootstrap Prerequisites: project-instructions, product-document, technical-context, project-plan.
sddp-systemdesign
Command description: Create or refine the canonical software architecture document. Argument hint: [project description, docs, constraints, or architecture inputs] Command category: project-bootstrap Prerequisites: none.