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 docs-sitegit 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/docs-site)<a href="https://agentmods.dev/skills/vpdpersonal/aspid.fasttools/docs-site"><img src="https://agentmods.dev/badge/skills/vpdpersonal/aspid.fasttools/docs-site/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/docs-site"><img src="https://agentmods.dev/badge/skills/vpdpersonal/aspid.fasttools/docs-site.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 58 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00116 | $0.07836 |
| Opus 5.5 | $0.00046 | $0.03134 |
| Sonnet 5.5 | $0.00023 | $0.01567 |
| Haiku 4.5 | $0.00012 | $0.00784 |
Grade A, and why
docs-site 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 — 374 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation site
One source of truth: Markdown in Website/. The same file is read by GitHub and by the Docusaurus site. Nothing is
copied by hand — the root README.md, the changelog page and the API reference are generated.
Write GitHub Flavored Markdown; the site adapts to it, never the other way round.
The UPM package (Aspid.FastTools/Packages/tech.aspid.fasttools/) ships no documentation pages or images: everything in
that folder reaches every consumer project through git subtree split in release.yml. It keeps only README.md
(a description and the site link; it gives no git URL, because a store buyer who follows one adds a second copy, and
no install steps, because whoever reads it has the package already). Samples~ ships no README: its description in package.json → samples ends with
Tutorial: https://vpdpersonal.github.io/Aspid.FastTools/tutorials/<slug>. The Package Manager shows that line as
text; the Welcome tab cuts it off the description (WelcomeView.SplitTutorialUrl) and shows a Tutorial link.
Never add an image, a full page or a sample README there.
Layout
| What | Source | Site route |
|---|---|---|
| Introduction | Website/docs/README.md |
/docs |
| Main docs | Website/docs/NN-*.md |
/docs/<name> (02-serializable-types.md → /docs/serializable-types) |
| Samples | Website/tutorials/<Sample>/README.md |
/tutorials/<slug> (SerializeReferences → serialize-references; an optional NN. folder prefix orders and is stripped) |
| Samples overview | Website/tutorials/index.mdx → <SamplesGallery/> |
/tutorials |
| Changelog | root CHANGELOG.md, Website/i18n/ru/CHANGELOG.md |
/changelog |
| API reference | generated into Website/api/ by DocFX (committed) |
/api |
| Translations | Website/i18n/ru/docusaurus-plugin-content-docs/current/**, …-docs-tutorials/current/** (same names) |
/ru/... |
| Interface strings | Website/i18n/ru/**/*.json (code.json, navbar.json, each plugin's current.json) |
|
| Images | Website/docs/Images/, Website/tutorials/<Sample>/Images/ |
referenced relatively |
| Root README | generated from Website/docs/README.md in GitHub's layout (committed); translations live on the site only |
— |
| Package README | Aspid.FastTools/Packages/tech.aspid.fasttools/README.md |
— |
| Package changelog | generated from the root CHANGELOG.md with its .meta by release.yml (scripts/package-changelog.mjs); gitignored, only the upm branches carry it; Unity's Package Manager reads it |
— |
| Site config | Website/docusaurus.config.js, sidebars.js, sidebarsTutorials.js, sidebarsApi.js |
|
| CI | .github/workflows/docs.yml → GitHub Pages https://vpdpersonal.github.io/Aspid.FastTools/ |
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 cd55684d16ae
- 4d ago Changed · +2 lines · +6 tokens per session db7bc414ea5d
- 6d ago Changed · -43 lines 407a58036af0
- 7d ago Changed · +2 lines 2f71cc7d0df0
- 11d ago Changed · +3 lines a997b7d6ac17
- 12d ago Changed · +19 lines · +4 tokens per session f7ae85ddb7f5
- 16d ago Changed · +14 lines 689cadb7d4db
- 18d ago Changed · +42 lines · +16 tokens per session 7576adacae36
- 19d ago Changed · -88 lines 42ab6d6dc204
- 22d ago First seen · 427 lines · 90 tokens per session scan A 875eb9de6d0a
docs-site is a skill published in the GitHub repository VPDPersonal/Aspid.FastTools (24 stars, last pushed today), licensed MIT. It adds 116 tokens to every session and 7,836 once invoked, about $0.0005 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-09-06.
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…
edit-scene
Creates and modifies Unity scene and prefab files. Use this skill whenever creating, editing, or modifying .unity scene files or .prefab prefab files. This includes adding GameObjects, building uGUI hierarchies, wiring up components, and any task that results in changes to .unity or .prefab files.