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/aws-samples/sample-strands-agent-with-agentcore/visualizationnpx skills add aws-samples/sample-strands-agent-with-agentcore --skill visualizationgit clone --depth 1 https://github.com/aws-samples/sample-strands-agent-with-agentcoreWhat 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.00018 | $0.00715 |
| Opus 5 | $0.00009 | $0.00358 |
| Sonnet 5 | $0.00004 | $0.00143 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
visualization 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 2d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visualization
When to Use This Skill
Use create_visualization when the user wants to visualize numerical data — comparisons, trends, distributions, or proportions.
| Use this skill for... | Use excalidraw skill for... |
|---|---|
| Sales figures by quarter | System architecture diagram |
| Survey response percentages | Flowchart or decision tree |
| Stock price over time | Sequence / interaction diagram |
| Market share breakdown | Mind map or concept map |
| Any x/y or segment/value data | Shapes, boxes, arrows, labels |
Available Tool
- create_visualization: Create a chart specification for frontend rendering.
Parameters (MUST match exactly)
| Parameter | Type | Required | Description |
|---|---|---|---|
chart_type |
str | Yes | "bar", "line", or "pie" |
data |
list[dict] | Yes | Array of data objects — see formats below |
title |
str | No | Chart title |
x_label |
str | No | X-axis label (bar/line only) |
y_label |
str | No | Y-axis label (bar/line only) |
Data Formats (CRITICAL — use exact field names)
Bar / Line charts — each object MUST have "x" and "y" keys:
[{"x": "Jan", "y": 100}, {"x": "Feb", "y": 150}, {"x": "Mar", "y": 120}]
Pie charts — each object MUST have "segment" and "value" keys:
[{"segment": "Category A", "value": 30}, {"segment": "Category B", "value": 70}]
Optional: add "color": "hsl(210, 100%, 50%)" to any data point for custom color.
Example tool_input
Bar chart:
{
"chart_type": "bar",
"data": [{"x": "Q1", "y": 250}, {"x": "Q2", "y": 310}, {"x": "Q3", "y": 280}],
"title": "Quarterly Revenue",
"x_label": "Quarter",
"y_label": "Revenue ($K)"
}
Pie chart:
{
"chart_type": "pie",
"data": [{"segment": "Mobile", "value": 60}, {"segment": "Desktop", "value": 35}, {"segment": "Tablet", "value": 5}],
"title": "Traffic by Device"
}
Common Mistakes to Avoid
- Do NOT use
{"labels": [...], "values": [...]}format — data MUST be a list of dicts. - Bar/line data MUST use
"x"and"y"keys, NOT"label"or"name".
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.
- 2d ago First seen · 79 lines · 18 tokens per session scan A 1d04fa703d1f
visualization is a skill published in the GitHub repository aws-samples/sample-strands-agent-with-agentcore (191 stars, last pushed 6d ago), licensed MIT. It adds 18 tokens to every session and 715 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
opencli-usage
Use at the start of any OpenCLI session — this is the top-level map of what opencli can do, how to discover adapters, what flags and output formats are universal, and which specialized skill to load next. Point here when an agent asks "what can opencli do?" or "how do I find the right command?".
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
opencli-browser-sitemap
Use when driving a website with opencli browser and sitemap context is available, requested, or needed to avoid blind navigation. Guides agents to consume site sitemap files lazily, choose adapter/browser fallback paths, resume from state signatures, and mark stale sitemap entries without trusting them over live…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
pinchtab-stealth-score
Run the PinchTab stealth-score sweep against 15 bot-detection / fingerprint sites (sannysoft, rebrowser, deviceandbrowserinfo, iphey, whoer, browserscan, pixelscan, fingerprint-scan, incolumitas, fvision, amiunique, browserleaks, creepjs, coveryourtracks, fingerprint-demo). Starts a Docker PinchTab container per…
openbot-data-access
Governs how the OpenBot browser app reads and writes server data — every request goes through client in app/src/lib/client.ts, every read is a queryOptions factory in app/src/lib/ /queries.ts, every write is a mutationOptions factory in app/src/lib/ /mutations.ts, and components consume them through…