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-player-buildsgit 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-player-builds)<a href="https://agentmods.dev/skills/vpdpersonal/aspid.fasttools/asp-ft-player-builds"><img src="https://agentmods.dev/badge/skills/vpdpersonal/aspid.fasttools/asp-ft-player-builds/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-player-builds"><img src="https://agentmods.dev/badge/skills/vpdpersonal/aspid.fasttools/asp-ft-player-builds.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.00099 | $0.01007 |
| Opus 5.5 | $0.00040 | $0.00403 |
| Sonnet 5.5 | $0.00020 | $0.00201 |
| Haiku 4.5 | $0.00010 | $0.00101 |
Grade A, and why
asp-ft-player-builds 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Player builds
The argument is the Unity version. No argument → the minimum: the first version of UNITY_VERSIONS in
.github/workflows/ci.yml.
When
- The manual QA of a stable release, before the merge of the release PR: the items "player builds on Mono and
IL2CPP", "non-development build", "IL2CPP stripping and
SerializableType" and "one standalone and one AOT target" of.github/ISSUE_TEMPLATE/release_checklist.yml. - A change to
SerializableType, the type lookup, the profiler marker generator orENABLE_PROFILERcode.
Run
Run it on the branch under test: for a release, a worktree of chore/release-<version>. The script builds the
package of its own checkout.
scripts/player-builds.sh <scratch>/player-builds [unity-version]
<scratch>/player-buildsmust not exist or be empty. It getsProject/,Builds/andLogs/.- Run it in the background: all four targets take about 3–4 minutes.
--targets mac-mono,ios-simlimits the run to the listed targets.- It needs an Apple Silicon Mac (the players are arm64), the Unity Editor of the version, its modules
mac-il2cppandios, and Xcode forios-sim. A missing module skips its target and prints the Unity Hub command that installs it. Ask the user before you run an install: it downloads gigabytes. - The simulator runs without its window. The script shuts it down after the run when it booted it.
Read the table
TARGET BUILD ERR/WARN AOTCHECK PROFILER REFERENCE MISSING
mac-mono Succeeded 0/0 5/5 off dev=off none
BUILD: theBuildReportresult.xcodebuild-failed: Unity made the Xcode project, Xcode did not build it.ERR/WARN: the errors and warnings of theBuildReport.AOTCHECK: the required fields that resolved in the player, out of all. Required are a[Preserve]class,Transform,List<int>, andLinePatternof the Types sample (samplePattern, andsamplePatternInstancefor its instance): each must resolve on every target. The sample patterns carry[Preserve], so aMISSINGthere means that the sample lost it.no-run: the player did not printAOTCHECK DONE.PROFILER:ENABLE_PROFILERandDEVELOPMENT_BUILDin the player. Both must beoff.REFERENCE MISSING: reference fields that did not resolve. They are informational and do not fail the run:plain, a class referenced only by its stored name: the linker removes it from Managed Stripping Level Medium up. The XML docs ofSerializableTypeBasesay so.plainthat turnsMISSINGonmac-monoormac-il2cpp-minimalis a regression.strippedEngine,BoxCollider: on every IL2CPP target Strip Engine Code removes the physics module, which the check scene does not use.
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 · 70 lines · 99 tokens per session scan A bf7b68c9d2d5
asp-ft-player-builds is a skill published in the GitHub repository VPDPersonal/Aspid.FastTools (24 stars, last pushed 2d ago), licensed MIT. It adds 99 tokens to every session and 1,007 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-25.
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.
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…
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 in the Unity Editor. This includes verifying implementations, debugging test failures, running specific test assemblies, or any task that involves the rununitytests…
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…
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…
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 .