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 wikipedia-itgit 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/wikipedia-it)<a href="https://agentmods.dev/skills/justvugg/tools-factory/wikipedia-it"><img src="https://agentmods.dev/badge/skills/justvugg/tools-factory/wikipedia-it.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.00036 | $0.00506 |
| Opus 5 | $0.00018 | $0.00253 |
| Sonnet 5 | $0.00007 | $0.00101 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
wikipedia-it 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 8d 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
wikipedia-it
Generated by Gutenberg. Use this skill to call the wikipedia-it API through the local wikipedia-it CLI.
When to use
- The user asks for data exposed by wikipedia-it (api).
- An agent task needs structured JSON from https://it.wikipedia.org.
- You need to perform a write/destructive operation on wikipedia-it — always preview first, run with
--yesonly on explicit user confirmation.
How to invoke
The skill assumes the generated CLI is on PATH (or invoke via scripts/use-go.sh run ./cmd/wikipedia-it from the project directory).
wikipedia-it operations
wikipedia-it call getPageSummaryBologna --json
wikipedia-it sync --json
wikipedia-it search "<keyword>" --json
Authentication
No authentication required.
Operations index
getPageSummaryBologna(GET /api/rest_v1/page/summary/Bologna) — read — GET /api/rest_v1/page/summary/BolognagetPageSummaryRoma(GET /api/rest_v1/page/summary/Roma) — read — GET /api/rest_v1/page/summary/RomagetPageRelatedItalia(GET /api/rest_v1/page/related/Italia) — read — GET /api/rest_v1/page/related/ItaliagetPageRandomSummary(GET /api/rest_v1/page/random/summary) — read — GET /api/rest_v1/page/random/summarygetFeedFeatured(GET /api/rest_v1/feed/featured/{year}/{month}/{day}) — read — GET /api/rest_v1/feed/featured/{year}/{month}/{day}
Output contract
- All commands accept
--jsonand emit machine-readable output. callreturns{ dryRun, operation, request, response }.dryRun: truemeans the call was not executed (write op without--yes).searchreturns cached records.syncpopulates the local SQLite cache.
Provenance
- Schema: gutenberg.blueprint.v1
- Generated by: gutenberg 0.3.0
- Source spec: /tmp/wiki4.openapi.json
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.
- 8d ago First seen · 52 lines · 36 tokens per session scan A 1e7b6f0447ff
wikipedia-it is a skill published in the GitHub repository JustVugg/tools-factory (52 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 506 once invoked, about $0.0002 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-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-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-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.
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.
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.