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 linkfox-ai/linkfox-skills --skill linkfox-sif-keyword-summarygit clone --depth 1 https://github.com/linkfox-ai/linkfox-skillsWrote 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/linkfox-ai/linkfox-skills/linkfox-sif-keyword-summary)<a href="https://agentmods.dev/skills/linkfox-ai/linkfox-skills/linkfox-sif-keyword-summary"><img src="https://agentmods.dev/badge/skills/linkfox-ai/linkfox-skills/linkfox-sif-keyword-summary/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/linkfox-ai/linkfox-skills/linkfox-sif-keyword-summary"><img src="https://agentmods.dev/badge/skills/linkfox-ai/linkfox-skills/linkfox-sif-keyword-summary.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 System Prompt Leakage · line 168 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
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.00222 | $0.03337 |
| Opus 5 | $0.00111 | $0.01669 |
| Sonnet 5 | $0.00044 | $0.00667 |
| Haiku 4.5 | $0.00022 | $0.00334 |
Grade A, and why
linkfox-sif-keyword-summary 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SIF Keyword Traffic Source Summary
This skill guides you on how to query and analyze keyword traffic source data for Amazon products, helping sellers understand the traffic structure behind keywords — including organic search, Sponsored Products (SP) ads, brand ads, video ads, and various Amazon recommendation placements.
Core Concepts
The SIF Keyword Summary tool returns, for one given keyword, the list of ASINs appearing under that keyword along with their per-keyword traffic exposure breakdown and their product-level cross-channel traffic mix. It answers: Who is taking traffic under this keyword, and through which channels?
Traffic channels analyzed:
- Natural Search — organic search result positions
- SP Ads (Sponsored Products) — paid product ad placements (regular slot)
- Brand Ads (SB) — top and bottom brand ad placements on the search results page
- Video Ads (SBV) — Sponsored Brands Video placements
- SP Recommendation slots — Trending now / Seen on social media / Customers frequently viewed / 4 stars and above
- Amazon's Choice (AC) — Amazon's Choice badge recommendations
- Editorial Recommendations (ER) — editorial/curated recommendation placements
- Top Rated (TR) — high-rating recommendation placements
Two score families (important — do not mix):
- Product-level fields (no prefix, e.g.
naturalSearchExposureScore): the ASIN's overall exposure across all keywords. - Keyword-level fields (
keyword…prefix, e.g.keywordNaturalExposureScore): the ASIN's exposure on just this one queried keyword.
Parameter Guide
Required Parameter
| Parameter | Type | Description |
|---|---|---|
| searchKeyword | string | The search keyword to analyze. Translate to the target marketplace's language when applicable. Max 1000 characters. |
Optional Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
| country | string | US | Marketplace code (13 supported — see list below). |
| asins | string | (none) | Comma-separated ASIN filter; if omitted, returns all ASINs appearing under the keyword. Max 1000 chars. |
| condition | string | (none) | Filter by a specific traffic source. Only one value per request. See Condition Filters below. |
| last7d | boolean | true | Use the latest 7 days. When false, the API uses startDate/endDate. |
| startDate | string | — | yyyy-MM-dd. Takes effect when last7d=false; if omitted, the system's latest integral week is used. |
| endDate | string | — | yyyy-MM-dd, paired with startDate. |
| sortBy | string | (default) | Sort field. See sortBy section below. |
| pageNum | integer | 1 | Page number for pagination. |
| pageSize | integer | 100 | Results per page. Min 10, max 100. |
| desc | boolean | true | Sort in descending order. |
What ships with it
4 files 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.
- 9d ago First seen · 234 lines · 222 tokens per session scan A dcf85e6e5750
linkfox-sif-keyword-summary is a skill published in the GitHub repository linkfox-ai/linkfox-skills (101 stars, last pushed 22d ago), licensed MIT. It adds 222 tokens to every session and 3,337 once invoked, about $0.0011 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…