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 IvanLi-CN/tavily-hikari --skill tavily-hikari-extractgit clone --depth 1 https://github.com/IvanLi-CN/tavily-hikariWrote 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/ivanli-cn/tavily-hikari/tavily-hikari-extract)<a href="https://agentmods.dev/skills/ivanli-cn/tavily-hikari/tavily-hikari-extract"><img src="https://agentmods.dev/badge/skills/ivanli-cn/tavily-hikari/tavily-hikari-extract/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/ivanli-cn/tavily-hikari/tavily-hikari-extract"><img src="https://agentmods.dev/badge/skills/ivanli-cn/tavily-hikari/tavily-hikari-extract.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Privilege Escalation · line 30 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00022 | $0.00203 |
| Opus 5 | $0.00011 | $0.00102 |
| Sonnet 5 | $0.00004 | $0.00041 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
tavily-hikari-extract 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 13d 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
Tavily Hikari Extract
Use this skill when the task needs content extraction from one or more URLs through Tavily Hikari.
Workflow
-
Confirm the URL list is specific and avoids private or irrelevant pages.
-
Run:
tvly-hikari extract https://example.com/article --json -
Save larger extraction output when it will be reused:
tvly-hikari extract https://example.com/article --json -o tavily-extract.json -
Use extracted text as supporting evidence, keeping quotes brief and source-specific.
Hikari Notes
- Requests go to the configured Hikari
/api/tavily/extractfacade. - The configured token is a Hikari access token.
- Hikari applies quota, audit logging, and upstream key-pool routing.
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.
- 13d ago First seen · 32 lines · 22 tokens per session scan A 2fff96723c16
tavily-hikari-extract is a skill published in the GitHub repository IvanLi-CN/tavily-hikari (348 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 203 once invoked, about $0.0001 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
status-card-query
Create and maintain agent-authored Paperclip status cards, or compile a prose interest prompt into bounded CompanySearchQuery objects and write the first summary from the assigned Summarizer run.
gpt-researcher
Autonomous deep research from Codex via MCP.
bilibili_search
Search for videos on Bilibili using keyword queries generated from user interests.
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-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…
site-config-creation
Create or update the [site] section of stencila.toml for published Stencila sites. Use when asked to configure site domain, title, author, logo, icons, labels, descriptions, socials, featured content, navigation, routes, access, layout presets and regions, glide, search, formats, reviews, uploads, remotes, actions…