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 VPDPersonal/Aspid.FastTools --skill asp-ft-releasegit clone --depth 1 https://github.com/VPDPersonal/Aspid.FastToolsWrote 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/vpdpersonal/aspid.fasttools/asp-ft-release)<a href="https://agentmods.dev/skills/vpdpersonal/aspid.fasttools/asp-ft-release"><img src="https://agentmods.dev/badge/skills/vpdpersonal/aspid.fasttools/asp-ft-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/skills/vpdpersonal/aspid.fasttools/asp-ft-release"><img src="https://agentmods.dev/badge/skills/vpdpersonal/aspid.fasttools/asp-ft-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.00098 | $0.04270 |
| Opus 5.5 | $0.00039 | $0.01708 |
| Sonnet 5.5 | $0.00020 | $0.00854 |
| Haiku 4.5 | $0.00010 | $0.00427 |
Grade A, and why
asp-ft-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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
The argument is the version, for example 1.0.0-rc.9. Remove a leading v. No argument → ask for the version.
Channel
The version picks the channel. It is the same rule as in scripts/set-version.sh and .github/workflows/release.yml.
- A version with a hyphen (
1.0.0-rc.9) →upm-preview: a Preview badge, a GitHub prerelease. - A version without a hyphen (
1.0.0) →upm: a stable release. Only it has the steps marked Stable.
Every version, on either channel, also publishes skills/ as the skills branch and the skills/<version> tag.
Which phase
Run git fetch origin. Then pick the phase:
- The tag
v<version>is on origin (git ls-remote --tags origin v<version>) → go to "Phase 3". - The
package.jsononorigin/mainhas the version → go to "Phase 2". - The PR from
chore/release-<version>is open (gh pr view chore/release-<version> --json state,url) → report its link and its checks, then stop. Stable: add the steps of "Asset Store upload". - Else → go to "Phase 1".
Phase 1: release PR
Do every step without questions. Stop at the first failure and report it.
-
Check that the working tree is clean.
-
Check that the version is greater than the
package.jsonversion onorigin/main. Use SemVer precedence:1.0.0-rc.10>1.0.0-rc.9, and1.0.0>1.0.0-rc.9. -
Create the branch:
git switch -c chore/release-<version> origin/main. -
Check that
Website/node_modulesexists. If not, runnpm --prefix Website ci. -
Run
scripts/set-version.sh <version>. Keep the "channel changed" line if the script prints it. -
Start two
unity-verifyagents in the background, with EditMode tests and no filter:- a project from
scripts/make-unity-test-project.sh <scratchpad>/unity-min <minimum>, where<minimum>is the first version of theunitymatrix in.github/workflows/ci.yml; - the dev project
Aspid.FastTools/of this checkout.
The
unity-verifyagent is user-level. Without it, run the batch command from the header ofscripts/make-unity-test-project.shfor both projects, in the background. - a project from
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 Changed · +4 lines 29b6f0e893b8
- 4d ago Changed · +20 lines 8518f85fdcfa
- 5d ago Changed · +62 lines 0ec4f1e47e39
- 6d ago Changed · +8 lines 133461d3c0bf
- 8d ago Changed · +1 lines b6f105f348a7
- 9d ago First seen · 126 lines · 98 tokens per session scan A 33be00113bcd
asp-ft-release is a skill published in the GitHub repository VPDPersonal/Aspid.FastTools (24 stars, last pushed today), licensed MIT. It adds 98 tokens to every session and 4,270 once invoked, about $0.0004 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-07.
Other skills, from other repositories
test-designing-guide
Provides test design methodology for Unity projects. Use this skill whenever designing test cases from requirements or specifications, including selecting test techniques, deriving test cases, and formatting them. Even for small features, load this skill to ensure test design rigor.
fix-bug
Diagnoses and fixes bugs using a test-first workflow (reproduce, diagnose, fix). Use this skill whenever the user reports a bug, describes unexpected behavior, or asks to investigate or fix a defect. Even if the user says "something's broken", "this isn't working", "fix this bug", or "why does X happen", load this…
refine-tests
Reviews existing test code for conformance to the test-designing-guide and test-writing-guide, then applies the refinements. Use this skill when the user wants to review or refine existing test code so it follows the project's test design and writing conventions. Typically invoked as /refine-tests .
test-writing-guide
Provides guidelines for writing test code for Unity projects. Make sure to use this skill whenever writing, creating, editing, or modifying test code files (files under Tests/). This includes implementing new tests, fixing test failures, adding test cases, or any task that results in test code changes. Even for small…
plan-feature
Orchestrates the test-first implementation planning workflow for feature implementation and spec changes. Use this skill whenever plan mode is active and the task involves implementing or adding a new feature, or changing an existing specification. Even if the user only says "plan this" or "how should we implement…
run-tests
Provides guidelines for running Unity tests using the rununitytests tool. Make sure to use this skill whenever running, executing, or re-running tests on the Unity editor. This includes verifying implementations, debugging test failures, running specific test assemblies, or any task that involves the rununitytests…