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 athola/skrills --skill html-portal-generatorgit clone --depth 1 https://github.com/athola/skrillsWrote 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/athola/skrills/html-portal-generator)<a href="https://agentmods.dev/skills/athola/skrills/html-portal-generator"><img src="https://agentmods.dev/badge/skills/athola/skrills/html-portal-generator/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/athola/skrills/html-portal-generator"><img src="https://agentmods.dev/badge/skills/athola/skrills/html-portal-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00040 | $0.02288 |
| Opus 5 | $0.00020 | $0.01144 |
| Sonnet 5 | $0.00008 | $0.00458 |
| Haiku 4.5 | $0.00004 | $0.00229 |
Grade A, and why
html-portal-generator 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 11d 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HTML Portal Generator
Convert any codebase into a single, self-contained HTML portal application. The output is one .html file with embedded styles, scripts, and data that works offline, on file:// protocol, and can be uploaded into AI application portals.
When to Use
- You have a codebase (CLI tool, library, API, framework) and need an interactive HTML representation of its functionality
- The HTML will be uploaded into a smart AI portal or application integration system
- You need all features to work standalone without a running server
- You want users to explore, validate, analyze, and interact with the product from a browser
Process
Follow these phases in order. Each phase builds on the previous.
Phase 1: Codebase Analysis
Understand what the product does before writing any HTML.
- Read project documentation: README, CLAUDE.md, architecture docs, changelogs
- Identify core crates/packages: Map each module's purpose and public API
- Catalog user-facing features: CLI commands, API endpoints, configuration options
- Extract data structures: Response types, configuration schemas, enum values
- Find existing UI code: Dashboards, templates, stylesheets (reuse their design language)
Produce a mental inventory:
- Feature list (what the product does)
- Data catalog (what entities/types exist)
- Command/API reference (how users interact)
- Visual identity (colors, fonts, layout patterns from existing UI)
Phase 2: Reference Analysis (if provided)
If the user provides a reference HTML app:
- Read the first and last ~3KB to understand structure (large files may be minified)
- Identify the design pattern: CSS variables, layout system, component structure
- Note the interaction model: controls bar, status bar, grid layout, tab navigation
- Extract the color palette and typography from CSS custom properties
Phase 3: Architecture Design
Design the portal as a single-page app with tab navigation.
Required structural elements:
- Sticky header with product name, version badge, and summary stats
- Tab navigation bar for switching between views
- Main container with
max-widthfor readability - Sticky status bar footer with links to docs/repo
- Toast notification system for user feedback
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.
- 11d ago First seen · 248 lines · 40 tokens per session scan A 4dd086488683
html-portal-generator is a skill published in the GitHub repository athola/skrills (69 stars, last pushed 7d ago), licensed MIT. It adds 40 tokens to every session and 2,288 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
neo-vue
Use this skill when building, debugging, refactoring, or reviewing Vue 3 applications, SFCs, Composition API, Pinia stores, Vue Router, Vite, or Vue+TypeScript code. Trigger when the project has .vue files or the user mentions Vue, Pinia, Composition API, Router, reactivity, or component architecture.
neo-dotnet-tag-helper
Use this skill when the user asks to design, implement, refactor, or review custom ASP.NET Core Tag Helpers in C#, including TagBuilder usage, strongly typed attributes, dependency injection, ProcessAsync, and reusable Razor UI behavior.
accessibility
Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
performance
Optimize web performance for faster loading and better user experience. Use when asked to "speed up my site", "optimize performance", "reduce load time", "fix slow loading", "improve page speed", or "performance audit".
core-web-vitals
Optimize Core Web Vitals (LCP, INP, CLS) for better page experience using field and lab evidence. Use when asked to "improve Core Web Vitals", "fix LCP", "reduce CLS", "optimize INP", "page experience optimization", or "fix layout shifts".
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use when the user asks to build landing pages, websites, dashboards, web components, or any frontend UI. Generates creative, polished code that avoids generic AI aesthetics.