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 VKirill/claude-lane-stack --skill tavilygit clone --depth 1 https://github.com/VKirill/claude-lane-stackWrote 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/vkirill/claude-lane-stack/tavily)<a href="https://agentmods.dev/skills/vkirill/claude-lane-stack/tavily"><img src="https://agentmods.dev/badge/skills/vkirill/claude-lane-stack/tavily/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/vkirill/claude-lane-stack/tavily"><img src="https://agentmods.dev/badge/skills/vkirill/claude-lane-stack/tavily.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 6 findings, 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 MCP Rug Pull · line 18 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium Data Exfiltration · line 41 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 41 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 68 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 77 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 68 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00091 | $0.01224 |
| Opus 5.5 | $0.00036 | $0.00490 |
| Sonnet 5.5 | $0.00018 | $0.00245 |
| Haiku 4.5 | $0.00009 | $0.00122 |
Grade A, and why
tavily scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sS -X POST https://api.tavily.com/search \ How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tavily
Host skill. Not the skills.sh tvly CLI pack. REST only.
Session agent: tavily (cc tavily). Copy-lead writes under .agents/copy/research/inbox/.
Key, in this order: $TAVILY_API_KEY if it is set (BB sessions get it from the Env Catalog); else the Env Catalog entry TAVILY_API_KEY (env_get); else, only in a terminal session outside BB, the file:
if [ -z "${TAVILY_API_KEY:-}" ] && [ -f ~/secrets/tavily.env ]; then set -a; source ~/secrets/tavily.env; set +a; fi
test -n "${TAVILY_API_KEY:-}" || { echo "MISSING TAVILY_API_KEY (env, Env Catalog or ~/secrets/tavily.env)"; exit 1; }
Inside a BB / Lane Pilot session do not read ~/secrets/tavily.env: the key is already in the session or in the Env Catalog. No key anywhere → stop and report. Do not print the key. Do not npx skills add.
Query = search string, < 400 chars, not an essay. Split fat questions into 2–4 calls.
One note per query. Never append to a single web.md.
if [ -d .agents/copy ]; then
INBOX=.agents/copy/research/inbox
else
INBOX=.agents/research/inbox
fi
STAMP=$(date +%F)-<slug>
mkdir -p "$INBOX"
Copy the research-note template to $INBOX/$STAMP.md. Dump JSON beside it as $STAMP.json. Add a row to .agents/copy/INDEX.md when that board exists. Do not dump raw HTML into chat.
search (default)
Facts, examples, language snippets, a handful of URLs. Seconds.
curl -sS -X POST https://api.tavily.com/search \
-H "Authorization: Bearer $TAVILY_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query":"<QUERY>","max_results":5,"search_depth":"basic","include_answer":true}' \
> "$INBOX/$STAMP.json"
Useful fields (omit if unused):
| Field | Values |
|---|---|
search_depth |
basic (default), advanced |
max_results |
1–20 |
topic |
general, news, finance |
time_range |
day, week, month, year |
include_domains / exclude_domains |
arrays of hosts |
include_raw_content |
false unless you need page text |
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 Changed · +2 lines · +24 tokens per session 805d792050b9
- 1mo ago First seen · 101 lines · 67 tokens per session scan A c6bb0cd1b5bd
tavily is a skill published in the GitHub repository VKirill/claude-lane-stack (122 stars, last pushed today), licensed MIT. It adds 91 tokens to every session and 1,224 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other skills, from other repositories
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
eval-agents
Audit custom subagent definitions for Claude Code (.claude/agents/.md) and Codex (.codex/agents/.toml): loadability against the native schema, description overlap, model tier, tool scope, and headless-safe instructions. Use when onboarding to a project with agents, after adding or importing agents, or when the parent…
self-assessment
Interactive skill assessment with personalized learning path generation.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
source-command-methodology-advisor
Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack.
git-ai-archaeology
Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.