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/dgouron/review-flow/tailwindnpx skills add DGouron/review-flow --skill tailwindgit clone --depth 1 https://github.com/DGouron/review-flowWrote 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/dgouron/review-flow/tailwind)<a href="https://agentmods.dev/skills/dgouron/review-flow/tailwind"><img src="https://agentmods.dev/badge/skills/dgouron/review-flow/tailwind.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.00029 | $0.01224 |
| Opus 5 | $0.00015 | $0.00612 |
| Sonnet 5 | $0.00006 | $0.00245 |
| Haiku 4.5 | $0.00003 | $0.00122 |
Grade A, and why
dashboard-styling 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dashboard Styling Guide
Note: ReviewFlow does not use TailwindCSS or React. The dashboard is built with plain HTML, CSS custom properties, and vanilla JavaScript. This skill covers the styling conventions for the dashboard.
Activation
This skill activates for:
- Creating or modifying dashboard UI elements
- Optimizing styles and performance
- Resolving layout/responsive issues
- Reviewing CSS conventions
Principles
CSS Custom Properties → Semantic naming → Consistent spacing
Always use existing CSS custom properties (design tokens) before adding new values.
Design Tokens
Available tokens
Tokens are defined as CSS custom properties in src/interface-adapters/views/dashboard/styles.css:
:root {
/* Backgrounds */
--nsc-bg-base: #0b1220;
--nsc-bg-elevated: #111a2b;
--nsc-bg-surface: #162235;
--nsc-bg-surface-strong: #1c2a40;
/* Borders */
--nsc-border-soft: rgba(163, 192, 224, 0.16);
--nsc-border-strong: rgba(163, 192, 224, 0.28);
/* Text */
--nsc-text-primary: #e8efff;
--nsc-text-secondary: #b2c1dd;
--nsc-text-muted: #8393b0;
/* Accent colors */
--nsc-focus: #7ad8ff;
--nsc-action: #60c7ff;
--nsc-warning: #f4bc71;
--nsc-success: #62d3a8;
--nsc-danger: #f07f88;
}
/* Use tokens */
background: var(--nsc-bg-surface);
color: var(--nsc-text-primary);
border: 1px solid var(--nsc-border-soft);
/* Avoid hardcoded values */
background: #162235;
color: #e8efff;
Best Practices
Naming conventions
Use semantic, BEM-inspired class names:
/* Good: semantic and descriptive */
.review-card { }
.review-card__header { }
.review-card__score { }
.review-card--critical { }
/* Bad: generic or cryptic */
.card1 { }
.blue-box { }
.mt20 { }
Property order
Recommended order in declarations:
- Layout (
display,flex,grid) - Positioning (
position,top,left) - Box model (
margin,padding,width,height) - Typography (
font-,text-,line-height) - Visual (
background,border,color) - Misc (
cursor,opacity,transition)
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 · 224 lines · 29 tokens per session scan A 2c35a0b8155f
dashboard-styling is a skill published in the GitHub repository DGouron/review-flow (42 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 1,224 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
selecting-vizro-charts
Use this skill when choosing chart types, applying Plotly Express conventions, configuring colors, building KPI cards, or adding tables (AG Grid) to Vizro dashboards. Activate when the user asks which chart fits their data, needs custom chart functions, wants to set colors or palettes, is creating KPI metric cards, or…
verify-changes
Verify a code change in this repo before committing or opening a PR. Use after editing collector (backend), web (frontend), shared package, or the Go agent — picks the minimal sufficient check set per touched area.
new-skill
Scaffold a new brooks-lint analysis skill so it passes npm run validate and npm run evals on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends…
monitor-webcams
Discover live webcams in a map viewport and resolve thumbnails or player URLs. Use when the user asks for visual context near a location, route, border, port, or city.
track-tariff-trends
Retrieve MFN applied tariff-rate timeseries for a reporting country — applied vs bound rates by year, plus the optional US effective tariff rate. Use when the user asks how a country's MFN tariffs have changed over time.
architecture-patterns
Architecture validation and patterns for clean architecture, backend structure enforcement, project structure validation, test standards, and context-aware sizing. Use when designing system boundaries, enforcing layered architecture, validating project structure, defining test standards, or choosing the right…