Borrowing it
Nothing to install: this file belongs to SCStelz/security-investigator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SCStelz/security-investigator/main/.github/skills/svg-dashboard/SKILL.mdgit clone --depth 1 https://github.com/SCStelz/security-investigatorWrote 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/scstelz/security-investigator/svg-dashboard)<a href="https://agentmods.dev/skills/scstelz/security-investigator/svg-dashboard"><img src="https://agentmods.dev/badge/skills/scstelz/security-investigator/svg-dashboard/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/scstelz/security-investigator/svg-dashboard"><img src="https://agentmods.dev/badge/skills/scstelz/security-investigator/svg-dashboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00132 | $0.05477 |
| Opus 5 | $0.00066 | $0.02738 |
| Sonnet 5 | $0.00026 | $0.01095 |
| Haiku 4.5 | $0.00013 | $0.00548 |
Grade A, and why
svg-dashboard 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 12d 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 — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SVG Dashboard Generator
Renders SVG data visualization dashboards — either from a skill's
svg-widgets.yamlmanifest (structured dashboards) or freeform from ad-hoc investigation data in context.
Mode Detection
Before rendering, determine which mode applies:
| Condition | Mode | Behavior |
|---|---|---|
User asks for a dashboard after a skill report AND the calling skill has an svg-widgets.yaml |
Manifest Mode | Read the YAML manifest → follow its layout exactly → deterministic dashboard |
| User asks to "visualize", "chart", or "create an SVG" from ad-hoc data in context (query results, investigation findings, inline tables) | Freeform Mode | Select widget types from the Component Library below based on data shape → creative layout |
No svg-widgets.yaml exists for the current workflow |
Freeform Mode | Same as above |
Decision flow:
1. Is there an svg-widgets.yaml for the current skill?
→ YES + user said "dashboard" or "SVG from the report" → Manifest Mode
→ NO → Freeform Mode
2. Does the user have structured data in context (query results, tables, metrics)?
→ YES → Freeform Mode (use data shape to pick widgets)
→ NO → Ask user what data to visualize
Manifest Mode — Structured Dashboard
Used when a skill provides an svg-widgets.yaml manifest (e.g., mcp-usage-monitoring, sentinel-ingestion-report).
Execution
Step 1: Read the calling skill's svg-widgets.yaml (widget manifest)
Step 2: Read this file's Rendering Rules below (component library + quality standards)
Step 3: Read the completed report file (data source)
— If same chat: report data is already in context
— If new chat: read the file path provided by user or find latest in the skill's reports/ subfolder
Step 4: Map manifest fields → report data using data_sources.field_mapping_notes
Step 5: Render SVG → save to the same directory as the report: {report_basename}_dashboard.svg
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.
- 12d ago First seen · 297 lines · 132 tokens per session scan A a1a9c447c218
svg-dashboard is a skill published in the GitHub repository SCStelz/security-investigator (245 stars, last pushed 4d ago), licensed MIT. It adds 132 tokens to every session and 5,477 once invoked, about $0.0007 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
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…