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/ymd38/dev-skills/yds-progress-dashboardnpx skills add ymd38/dev-skills --skill yds-progress-dashboardgit clone --depth 1 https://github.com/ymd38/dev-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/ymd38/dev-skills/yds-progress-dashboard)<a href="https://agentmods.dev/skills/ymd38/dev-skills/yds-progress-dashboard"><img src="https://agentmods.dev/badge/skills/ymd38/dev-skills/yds-progress-dashboard.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.1 | $0.00096 | $0.01220 |
| Opus 5 | $0.00048 | $0.00610 |
| Sonnet 5 | $0.00019 | $0.00244 |
| Haiku 4.5 | $0.00010 | $0.00122 |
Grade A, and why
yds-progress-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 5d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: Engineering Metrics Dashboard Generator
You generate a self-contained, interactive HTML dashboard that visualizes code quality and security improvement progress over time. The dashboard reads JSON summary files produced by the yds-software-evaluation and yds-vulnerability-scan skills.
Phase 1: Data Collection
1.1 Locate JSON Summary Files
Scan for JSON files in:
docs/evaluation/*.json— software evaluation summariesdocs/security-audit/*.json— vulnerability scan summaries
If no JSON files exist, inform the user that they need to run yds-software-evaluation and/or yds-vulnerability-scan first with JSON output enabled.
1.2 Parse & Validate
For each JSON file, verify:
schemaVersionis"1.0"typeis either"software-evaluation"or"vulnerability-scan"dateis a valid ISO date string- Required fields are present (scores for evaluation, findings for vulnerability)
Sort all entries by date ascending. Group by target if multiple targets exist.
Phase 2: Dashboard Generation
2.1 Technology
Generate a single self-contained HTML file with:
- Chart.js via CDN (
https://cdn.jsdelivr.net/npm/chart.js) for charts - Inline CSS for styling (dark theme, responsive)
- Inline JavaScript for data processing and chart rendering
- No build step required — open directly in any browser
2.2 Dashboard Sections
The HTML must include these sections:
Header
- Project name (derived from target names)
- Date range of available data
- Last updated timestamp
1. Quality Score Trend (Line Chart)
- X-axis: dates
- Y-axis: score (0–10)
- Lines: one per pillar (Architecture, Reliability, Observability, Security, DX) + Overall
- Tooltip: show exact score and date
- Color-coded by pillar
2. Latest Score Radar Chart
- Compare the most recent evaluation against the previous one
- 5 axes for the 5 pillars
- Two overlaid datasets: "Current" (solid) vs "Previous" (dashed)
- If only one evaluation exists, show only "Current"
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.
- 5d ago First seen · 148 lines · 96 tokens per session scan A 62a4f233ecca
yds-progress-dashboard is a skill published in the GitHub repository ymd38/dev-skills (4 stars, last pushed 8d ago), licensed MIT. It adds 96 tokens to every session and 1,220 once invoked, about $0.0005 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-31.
Other skills, from other repositories
weather-fetcher
Instructions for fetching current weather temperature data for Dubai, UAE from Open-Meteo API.
precommit
Run every dbatools quality gate on demand before committing — style scan, command registration, TODO sweep, and a codex review of the working diff.
claude-md-review
Audit a CLAUDE.md file for the patterns that actually degrade Claude Code's output — vagueness, unnamed files, stale facts, and bloat. Use when asked to review, audit, improve, shrink, or fix a CLAUDE.md, and when a project's results feel inconsistent or Claude keeps rediscovering the same context.
best-practices
Searchable knowledge base of 152+ programming best practices across 30+ languages and frameworks. BM25-powered search over curated resources from industry leaders (Google, Airbnb, Uber, Mozilla, Shopify, OWASP).
brainstorm-feature
Clarify a rough product or engineering idea into a BRD-lite brief (Why) with measurable business value.
implementation-readiness
Verify BRD-lite, PRD, SRS/FRS, UX, and test prerequisites before implementation starts.