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/codeinfinity1/stram/frontend-designnpx skills add CodeInfinity1/Stram --skill frontend-designgit clone --depth 1 https://github.com/CodeInfinity1/StramWhat 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 | $0.00026 | $0.00401 |
| Opus 5 | $0.00013 | $0.00200 |
| Sonnet 5 | $0.00005 | $0.00080 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
frontend-design 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 2d 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.
What it actually says
Frontend Design
Purpose
Build usable interfaces, not placeholder pages. This skill guides product screens, dashboards, tools, and frontend changes with empathy, domain fit, and verification.
When To Use
Use for UI builds, redesigns, frontend polish, app screens, visual QA, responsive layout, and product-flow improvements.
Inputs And Evidence
- Product domain, audience, existing design system, screenshots, current UI code, and interaction goals.
- Browser observations, screenshots, and test results.
Tool Map
read_filesearch_workspacebrowser_live_openbrowser_live_observebrowser_live_screenshotlive-browser-testingcodebase-inspection
Workflow
- Inspect existing frontend patterns before designing.
- Match density, tone, layout, and controls to the domain.
- Build the actual usable screen first, not a marketing shell.
- Keep interactions discoverable and ergonomic.
- Verify in browser with screenshots/observations.
- Fix responsive text/layout overlap before calling done.
Native Implementation Boundaries
- Use repo-native frontend code and Stram browser tools.
- Do not import Anthropic frontend-design or external reference design code.
- Generated visual references may inspire, but implementation must be project-owned.
Safety And Approval
- Avoid hiding important actions.
- Do not add unrelated dependencies without approval.
- Preserve existing design conventions unless the task asks for a redesign.
Verification
- Browser evidence should prove the UI renders.
- Check desktop/mobile where relevant.
- Report any unverified viewports or interactions.
Failure Modes
- Generic landing-page output for a tool/app.
- Pretty but unusable controls.
- No real browser verification.
References
- Shortlist item:
frontend-design.
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.
- 2d ago First seen · 67 lines · 26 tokens per session scan A ae7ec2f77293
frontend-design is a skill published in the GitHub repository CodeInfinity1/Stram (10 stars, last pushed 22d ago), licensed MIT. It adds 26 tokens to every session and 401 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-31.
Other skills, from other repositories
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
golden-rss
Use when testing the rss golden build.
omh-code-review
This is a Hermes-native code-review workflow skill.
redteam-web-detail-pack
Routing and boundary guidance for authorized general web application security testing. Use as a web testing router when the attack surface should be dispatched to more specific web vulnerability skills.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
studio
Architecture Studio control plane — initialize or inspect a studio workspace, create and register projects, or route an architecture/AEC task to the right agent or skill. Use when the user runs /as:studio, asks to set up or open their studio, manage its projects, or describes a task without naming a skill.