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 atretyak1985/swarmery --skill html-reportinggit clone --depth 1 https://github.com/atretyak1985/swarmeryWrote 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/atretyak1985/swarmery/html-reporting)<a href="https://agentmods.dev/skills/atretyak1985/swarmery/html-reporting"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/html-reporting/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/atretyak1985/swarmery/html-reporting"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/html-reporting.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.00046 | $0.00861 |
| Opus 5.5 | $0.00018 | $0.00344 |
| Sonnet 5.5 | $0.00009 | $0.00172 |
| Haiku 4.5 | $0.00005 | $0.00086 |
Grade A, and why
html-reporting 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 1mo 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Wrap already-authored content in one reusable, self-contained HTML shell —
inline CSS, no external assets, no build step — so every report an agent emits
shares one visual language: a dark terminal theme with severity-coded cards,
metric tables, and collapsible sections. Used by the session-closeout skill's
Phase 8 dashboard and @code-reviewer's Phase 5 audit.
Presentation only. This skill never gathers data, measures anything, or computes a number — the caller supplies the content and this skill renders it.
Rules (never violate)
- Never fabricate a metric or a health score; format only what the caller passed.
- Keep the file self-contained — no CDN link, no external
src/href, no<script>unless explicitly required. - Use the canonical shell verbatim and its severity classes; never re-style a report or hand-roll inline colors.
- Markdown stays the canonical artifact; the HTML is its optional mirror.
- Respect the body budget —
<main>≤ 300 lines (summary) / ≤ 500 (audit); consolidate rather than pad, and never leave a{{…}}placeholder. - No secrets or PII in the output; verify the written file is non-empty.
Resources
- Read
resources/shell.mdwhen rendering: the canonical HTML shell to copy verbatim plus the content-to-component map. - Read
resources/render-procedure.mdfirst: the input table, the two section skeletons (summary, audit), the 5-step procedure, the self-check, common mistakes, and a worked example.
How to use
What it does
Turns content you already wrote into a single self-contained HTML page that opens offline in any browser and survives being copied between machines.
When to use it
- An agent finished its analysis and wants a browsable page rather than terminal text.
- You are rendering a task summary dashboard — status header, metrics, per-role guidance.
- You are rendering an audit report with a health score and a P0–P3 backlog.
- A report runs past three sections, or will be read outside the terminal.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 90 lines · 46 tokens per session scan A ee96533bc26e
html-reporting is a skill published in the GitHub repository atretyak1985/swarmery (7 stars, last pushed today), licensed Apache-2.0. It adds 46 tokens to every session and 861 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
commit-message
Use ANY time the user signals they want to commit staged changes — including bare "commit", "/commit", "commit this", "commit these changes", "let's commit", "make a commit", "git commit", "write a commit message", "make a conventional commit", "use conventional commits", or any equivalent phrasing in context (e.g.…
dependency-versions
MUST consult this skill before answering whenever the user's task involves external versioned dependencies — even if you think you can handle it directly. This applies to: checking if packages/tools are up to date, upgrading npm/pip/cargo/go dependencies, planning or writing CI/CD workflows (GitHub Actions, CircleCI…
finish
Ship phase — merge, PR, keep, or discard with pre-merge verification.
gws-quick-ref
Quick reference for gws CLI syntax — core patterns, key flags, pagination, field masks, and output formats.
excalidraw
Create or extend editable Excalidraw diagrams from descriptions or repository evidence using a local skeleton-to-scene converter.
gws-events-subscribe
Google Workspace Events: Subscribe to Workspace events and stream them as NDJSON.