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 agentmods add skills/topviewai/skill/topview-amazon-opsnpx skills add topviewai/skill --skill topview-amazon-opsgit clone --depth 1 https://github.com/topviewai/skillWrote 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/topviewai/skill/topview-amazon-ops)<a href="https://agentmods.dev/skills/topviewai/skill/topview-amazon-ops"><img src="https://agentmods.dev/badge/skills/topviewai/skill/topview-amazon-ops.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 | $0.00131 | $0.00737 |
| Opus 5 | $0.00066 | $0.00368 |
| Sonnet 5 | $0.00026 | $0.00147 |
| Haiku 4.5 | $0.00013 | $0.00074 |
Grade A, and why
topview-amazon-ops 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 3d 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.
3. **Do not** run `scripts/mcp_call.py`, open SSE yourself, or use curl/raw HTTP. How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Topview Amazon Ops
Public Amazon market / ASIN / keyword intelligence through the host's unified topview-mcp server (progressive disclosure; domain amazon).
Step 0 — Bootstrap
- Confirm the host already has MCP server
topview-mcpconnected (look foruse_amazon_data,get_tool_schema,call_tool). - If tools are missing, tell the user to add the server from repo
mcp.example.jsoninto~/.cursor/mcp.json, reload MCP — then retry. - Do not run
scripts/mcp_call.py, open SSE yourself, or use curl/raw HTTP.
Execution
Server: topview-mcp (unified). Never open SSE yourself.
Amazon data tools are deferred — they do not appear as top-level tools/list entries. Invoke via progressive disclosure:
- Read the
use_amazon_datadescription ontools/list(embedded Tools catalog). Callinguse_amazon_dataonly to list tools is optional; call it once if the catalog says it is not loaded yet (Amazon proxy warm-up). - Pick a deferred tool name from the catalog or references/tool_routing.md.
get_tool_schemawith{ "name": "<deferred>", "domain": "amazon" }.call_toolwith{ "name": "<deferred>", "domain": "amazon", "arguments": { ... } }.
Typical host tool ids: mcp__topview-mcp__get_tool_schema / mcp__topview-mcp__call_tool (Cursor may prefix user-).
Do not assume deferred names like market_research are direct top-level tools. Creative tools (topview_* / ta_*) are on the same server but belong to topview-generate — call those directly, never via call_tool.
UX Rules
- Be concise; lead with findings, not RPC noise.
- Ask for marketplace / category / ASIN / keyword when required by the tool schema.
- Never invent private Seller Central Ads/order/profit numbers.
- Match the user's language.
- After analysis, if the user wants creatives, chain to
topview-generate.
Source
Routing adapted from Marketing Studio Amazon expert skills (V032).
What ships with it
1 file 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.
- 3d ago First seen · 57 lines · 131 tokens per session scan A 538ae26f62ac
topview-amazon-ops is a skill published in the GitHub repository topviewai/skill (35 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 131 tokens to every session and 737 once invoked, about $0.0007 per session on Opus 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…