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 JustVugg/tools-factory --skill multi-demogit clone --depth 1 https://github.com/JustVugg/tools-factoryWrote 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/justvugg/tools-factory/multi-demo)<a href="https://agentmods.dev/skills/justvugg/tools-factory/multi-demo"><img src="https://agentmods.dev/badge/skills/justvugg/tools-factory/multi-demo.svg" alt="Measured on agentmods" 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.00056 | $0.00337 |
| Opus 5 | $0.00028 | $0.00169 |
| Sonnet 5 | $0.00011 | $0.00067 |
| Haiku 4.5 | $0.00006 | $0.00034 |
Grade A, and why
multi-demo 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 7d 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.
What it actually says
Multi-source demo aggregator
Generated by Gutenberg. Use this skill to run the local multi-demo aggregator CLI across multiple API sources and return one merged JSON result.
When to use
- The user asks for a cross-source view covered by espn, open-meteo.
- An agent task needs one command that fans out to multiple APIs and ranks or merges the results.
How to invoke
multi-demo sources
multi-demo fan-out --json
multi-demo fan-out --param key=value --json
Sources
espn— espn; operation: getApisSiteV2SportsBasketballNbaScoreboard; base: https://site.api.espn.comopen-meteo— open-meteo; operation: getV1Forecast; base: https://api.open-meteo.com
Output contract
sourceslists the embedded source manifests.fan-out --jsonreturns merged/ranked items from each source.- Source-specific credentials use each source env prefix, not the aggregator prefix.
Provenance
- Schema: gutenberg.aggregator-manifest.v1
- Merge strategy: concatenate
- Rank strategy: by-source-order
- Example source: espn getApisSiteV2SportsBasketballNbaScoreboard
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.
- 7d ago First seen · 40 lines · 0 tokens per session scan A b1f5c1997b3b
multi-demo is a skill published in the GitHub repository JustVugg/tools-factory (52 stars, last pushed 2mo ago), licensed MIT. It adds 56 tokens to every session and 337 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
vs-product-qa
Answer Viking AI Search product questions, CLI usage questions, API/auth questions, configuration questions, and troubleshooting questions by grounding every claim in either the installed vs CLI's own output or official Volcengine documentation. Never fabricate.
vs-search-tuning-specify-policy-direction
Viking Search tuning for specified policy directions. Use this when the user provides specific queries, a type of query, or a business policy direction, and asks to boost, suppress, or fix a class of search results through request-parameter passthrough. You must only perform read-only baseline evaluation and…
vs-crawler
Crawl websites (news, blogs, papers, GitHub, product docs, RSS feeds) into a fixed-schema JSONL file, then create a dataset and a searchable application in Viking AI Search. Supports one-time crawl and scheduled recurring crawl with automatic incremental sync.
vs-search-tuning-partial-case
Use when the user provides 1-50 concrete bad-case search queries for one Viking Search app and wants local deterministic fixes. This skill only verifies request-level fine-operation interventions against a read-only baseline scene and delivers a console-ready configuration sheet, validated payloads, and a replay…
vs-user-onboarding
Guide a brand-new SearchCLI/vs user from first-time usage questions to sign-up, purchase of Viking AI Search, AK/SK setup, and a working authenticated CLI. Use when the user says they downloaded or installed SearchCLI/vs and asks how to use it, how to start, sign up, buy, or onboard.
volcengine-documentation
Volcengine official documentation lookup helper. Supports both document search and full-content fetch across Volcengine products, developer tools, support content, best practices, pricing, deployment, troubleshooting, API, SDK, and policy pages.