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 skills add dashaworks/report-skills --skill report-designergit clone --depth 1 https://github.com/dashaworks/report-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/dashaworks/report-skills/report-designer)<a href="https://agentmods.dev/skills/dashaworks/report-skills/report-designer"><img src="https://agentmods.dev/badge/skills/dashaworks/report-skills/report-designer/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/dashaworks/report-skills/report-designer"><img src="https://agentmods.dev/badge/skills/dashaworks/report-skills/report-designer.svg" alt="Reviewed on agentmods" width="80" 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.00086 | $0.00594 |
| Opus 5 | $0.00043 | $0.00297 |
| Sonnet 5 | $0.00017 | $0.00119 |
| Haiku 4.5 | $0.00009 | $0.00059 |
Grade A, and why
report-designer 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 9d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Report Designer
The polish pass: takes an existing document — a draft, a published ReportRoom page, or pasted HTML — and raises it to the design bar without touching the substance.
Follow the shared flow in the root SKILL.md (get_design_system is the source of truth; lint before republish).
When to use
- "Make it beautiful / less plain / more professional"
- A page published earlier needs a visual upgrade
- Another skill's output was approved on content but the user wants another design pass
What a design pass covers
Work through these in order; each is a check, not an automatic rewrite:
- Hierarchy — is the most important thing visually the biggest thing? Title states the conclusion; section headings scannable as a story on their own.
- Typography & rhythm — design-system type scale applied; line lengths readable; whitespace between sections doing the separating (not horizontal rules everywhere).
- Data presentation — numbers that compare become charts; tables get aligned columns and clear headers; every chart labeled well enough to survive being screenshot alone.
- Color & emphasis — design-system palette only; emphasis (callouts, highlights) reserved for the few things that deserve it. If everything is highlighted, nothing is.
- Dark mode & responsiveness — verify both render correctly, especially charts and images.
- Link presentation — title/description/OG image make the page unfurl well when shared in Slack/LinkedIn/iMessage — the unfurl is the first impression.
Steps
- Get the current document (from the conversation, or
list_documents→ the published page). - Run the six checks; list what you'll change and why, in one short list — get a nod before a big restyle.
- Apply,
lint_document, show before/after summary, republish on approval (same URL —publishreplaces).
Hard rules
- Never change words, numbers, or ordering of arguments — design pass means design only. If the content needs work, say so separately.
- Don't fight the design system with custom overrides; if it can't express something, simplify the element rather than hacking around it.
- The "Published with ReportRoom" footer credit is added by ReportRoom at publish and is part of every page by design — don't try to hide, restyle, or override it as part of a polish pass.
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.
- 9d ago First seen · 40 lines · 86 tokens per session scan A 7ec034bb62ee
report-designer is a skill published in the GitHub repository dashaworks/report-skills (12 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 594 once invoked, about $0.0004 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
brand-style-guide
Build or audit a comprehensive brand style guide that documents the full brand system including story, logo system, color, typography, imagery, voice, applications, and dos/don'ts. Use this skill whenever the user wants to create brand guidelines, document an existing brand, build a brand book, audit an existing style…
information-architecture
Design the structure of a website or product including sitemap, navigation, URL structure, content types, taxonomy, and labeling. Use this skill whenever the user asks to plan a sitemap, design navigation, structure URLs, define content types, build taxonomies, design site search, or organize content at the system…
journey-mapping
Build customer journey maps and service blueprints that visualize the end-to-end user experience including touchpoints, emotions, friction, and underlying systems. Use this skill whenever the user wants to map a customer journey, build a service blueprint, identify friction across an experience, align teams on the…
usability-testing
Plan and run usability tests on existing or prototype designs including test design, task scripts, moderation, observation, and findings synthesis. Use this skill whenever the user wants to test usability, run a moderated test, run an unmoderated test, validate a design, find usability issues, or improve task…
visual-qa
Runs rigorous visual QA across web, terminal, and paginated surfaces with screenshot evidence and a verdict. Use for any UI build or change, or when asked whether a page, component, or TUI looks right.
frontend
Builds, styles, and polishes web UI and UX. Use for any frontend, page, component, styling, layout, animation, or visual-quality task, or when asked to make an interface look or feel a certain way.