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.svg" alt="Measured on agentmods" 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.00086 | $0.02385 |
| Opus 5 | $0.00043 | $0.01192 |
| Sonnet 5 | $0.00017 | $0.00477 |
| Haiku 4.5 | $0.00009 | $0.00238 |
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 yesterday.
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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation site
One source of truth: Markdown files inside the UPM package. The same file is read by GitHub, by Unity
(as a TextAsset in the Inspector) and by the Docusaurus site in Website/. Nothing is copied by hand
and the root README.md is only an overview with links. Write GitHub Flavored Markdown; the site adapts
to it, never the other way round.
Layout
| What | Where | Site route |
|---|---|---|
| Main docs | Aspid.FastTools/Packages/tech.aspid.fasttools/Documentation/NN-*.md |
/docs/<name> (02-serializable-types.md → /docs/serializable-types) |
| Introduction | Documentation/README.md |
/docs |
| Tutorials | Samples~/<Sample>/README.md and TUTORIAL.md |
/tutorials/<slug>, /tutorials/<slug>/tutorial (SerializeReferences → serialize-references; an optional NN. folder prefix orders and is stripped) |
| Translations | Documentation/ru/** (same names), Samples~/<Sample>/README.ru.md, TUTORIAL.ru.md |
/ru/... |
| Images | Documentation/Images/ |
referenced relatively |
| Site config | Website/docusaurus.config.js, sidebars.js, sidebarsTutorials.js |
|
| CI | .github/workflows/docs.yml → GitHub Pages https://vpdpersonal.github.io/Aspid.FastTools/ |
The site folder is Website/, not Docs/: the repo already has docs/ (internal working documents) and
macOS treats the two names as one directory.
Two docs plugin instances: the default one (docs) points at Documentation/ (translation folders and
SUMMARY.md excluded), the second (id: 'tutorials') points at Samples~/ with
include: ['*/README.md', '*/TUTORIAL.md']. Scripts, scenes and .meta files are never touched.
Website/scripts/sync-i18n.mjs (run by prestart/prebuild) copies Documentation/<locale>/, every
*.<locale>.md in a sample root, and Documentation/Images/ into the Website/i18n/ layout Docusaurus expects.
Website/i18n/ is a build artifact and is gitignored; never edit it by hand.
SUMMARY.md is the GitHub table of contents; the site sidebar is autogenerated from the folder.
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.
- yesterday First seen · 147 lines · 86 tokens per session scan A 4da1549c018b
docs-site is a skill published in the GitHub repository VPDPersonal/Aspid.FastTools (24 stars, last pushed yesterday), licensed MIT. It adds 86 tokens to every session and 2,385 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-09-06.
Other skills, from other repositories
uloop-get-project-info
Get Unity project information via uloop CLI. Use when you need to check project settings, Unity version, platform, or other project metadata.
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…
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…
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 .