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 ScriptedAlchemy/agent-bundle --skill vendored-assetsgit clone --depth 1 https://github.com/ScriptedAlchemy/agent-bundleWrote 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/scriptedalchemy/agent-bundle/vendored-assets)<a href="https://agentmods.dev/skills/scriptedalchemy/agent-bundle/vendored-assets"><img src="https://agentmods.dev/badge/skills/scriptedalchemy/agent-bundle/vendored-assets/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/scriptedalchemy/agent-bundle/vendored-assets"><img src="https://agentmods.dev/badge/skills/scriptedalchemy/agent-bundle/vendored-assets.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.00041 | $0.00586 |
| Opus 5.5 | $0.00016 | $0.00234 |
| Sonnet 5.5 | $0.00008 | $0.00117 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
vendored-assets 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 1mo 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.
This is a copy
100% identical to vendored-assets — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Treat upstream artifacts as supply-chain inputs. Change their generator or documented import source, then regenerate; generated output is review evidence, not an editing surface.
Workflow
- Trace ownership. Identify the artifact, generator or exact import procedure, upstream source/version, license, consumers, tests, and shipped package or bundle. Search by asset and upstream project name to find current packaging scripts, generated artifacts, consumers, and history. Continue when every input and consumer is accounted for.
- Pin provenance. Resolve moving URLs, tags, branches, and omitted versions to an immutable release or artifact. Record project, version, path or URL, and digest in the generator or maintenance header. Omit a digest only when another enforced immutable source is recorded. Continue when a future run cannot silently select different bytes.
- Clear the license gate. Verify release metadata, license files, bundled notices, and the license trail retained in the distributed form. Continue when every distributed artifact has a verified retained license trail.
- Regenerate. Improve the generator or import reference first. Recover an exact procedure for generatorless assets; add a deterministic script only for recurring updates. Record a one-off procedure beside the artifact. A clean rerun must produce no diff.
- Audit the complete diff. Account for behavior, URLs and runtime fetches, source maps, notices, encoding, format changes, and additions or removals. For browser assets, also read browser-assets.md. Continue when every change is attributable and suspicious content is resolved or reported.
- Clear test and size gates. Record byte sizes before and after, use focused consumer tests, and compare bundle size or composition when shipped JavaScript, CSS, or registry output changes materially. Compare that output against the pre-update revision rather than measuring only current size. Continue when focused checks pass and every non-trivial size delta is explained.
- Close release impact. Apply root changeset routing for consumer-visible behavior, browser support, wire data, or meaningful shipped-size changes. Generated sections owned by barrels, AI docs, or migration tooling remain with the owners named in root instructions.
The task is complete when every input and consumer is accounted for, provenance and licenses are immutable and retained, regeneration is deterministic, every output change and non-trivial size delta is explained, focused checks pass or are reported as not runnable, and release impact is recorded.
What ships with it
1 file 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.
- 1mo ago First seen · 48 lines · 41 tokens per session scan A b45cfc17cce2
vendored-assets is a skill published in the GitHub repository ScriptedAlchemy/agent-bundle (11 stars, last pushed 5d ago), licensed Apache-2.0. It adds 41 tokens to every session and 586 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to vendored-assets, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…