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/juspay/xyne-spaces/data-visualizationnpx skills add juspay/xyne-spaces --skill data-visualizationgit clone --depth 1 https://github.com/juspay/xyne-spacesWhat 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.00031 | $0.00217 |
| Opus 5 | $0.00015 | $0.00109 |
| Sonnet 5 | $0.00006 | $0.00043 |
| Haiku 4.5 | $0.00003 | $0.00022 |
Grade A, and why
data-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 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.
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.
What it actually says
Data visualization
Choose the simplest visual that reveals the relationship.
- Comparison: bars. Trend: lines or areas. Composition: stacked bars or a small number of slices. Relationship: scatter. Flow or architecture: node-link diagram. Exact lookup: table.
- Label axes, units, periods, and sources. Start quantitative bar axes at zero unless a clearly explained exception is essential.
- Use color consistently and sparingly; do not encode crucial differences only through hue.
- Put the key takeaway near the visual and annotate meaningful changes.
- Avoid fabricated values. If the brief provides no data, use an explicitly labeled illustrative dataset or design an empty state.
- Make charts reflow without shrinking labels into illegibility.
Use native HTML/CSS/SVG for self-contained artifacts. Keep SVG text accessible and provide an adjacent textual summary for complex visuals.
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 · 24 lines · 31 tokens per session scan A 85d1cdabe258
data-visualization is a skill published in the GitHub repository juspay/xyne-spaces (134 stars, last pushed 3d ago), licensed Apache-2.0. It adds 31 tokens to every session and 217 once invoked, about $0.0002 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
create-demo
Guided wizard for creating RangeLink demo videos and promotional materials.
tcs-definition
Draft new QA test cases for the current issue and insert approved ones into qa-test-cases.yaml. Iteration loop draft → review → approve. Pairs with tc-implement.
affected-tests
Generate a compact grep-based affected tests for all integration tests changed on the current branch. Appends a "Affected Tests" block to the finish-issue note.
release-prep
Finish release tracking after release:lock has run: create the couimet.github.io article-registration issue, add it to the release board, and report all tracking issue URLs. Argument: target version X.Y.Z.
github-issues
Conventions for creating GitHub issues — labels, sub-issues, and content rules. Auto-consulted when Claude creates or modifies issues.
start-issue-hook
QA test case coverage requirements for /start-issue plans. Surfaces /tcs-definition during planning.