Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/dork-labs/dorkosnpx agentmods add skills/dork-labs/dorkos/maintaining-dev-playgroundWrote 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/dork-labs/dorkos/maintaining-dev-playground)<a href="https://agentmods.dev/skills/dork-labs/dorkos/maintaining-dev-playground"><img src="https://agentmods.dev/badge/skills/dork-labs/dorkos/maintaining-dev-playground/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/dork-labs/dorkos/maintaining-dev-playground"><img src="https://agentmods.dev/badge/skills/dork-labs/dorkos/maintaining-dev-playground.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 58 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 60 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 61 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 62 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00095 | $0.04022 |
| Opus 5.5 | $0.00038 | $0.01609 |
| Sonnet 5.5 | $0.00019 | $0.00804 |
| Haiku 4.5 | $0.00010 | $0.00402 |
Grade A, and why
maintaining-dev-playground 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 — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintaining the Dev Playground
The Dev Playground (apps/client/src/dev/, accessible at /dev in development) is a living gallery of every visual component in DorkOS. It exists so that designers and developers can review components in isolation, catch regressions visually, and verify that the design system is coherent.
The playground is only useful if it stays in sync with the actual application. Stale or missing showcases erode trust and let regressions slip through. This skill exists to prevent that drift.
When This Skill Applies
Assess playground impact whenever you edit files in:
apps/client/src/layers/widgets/**/ui/**— widget UI componentsapps/client/src/layers/features/**/ui/**— feature UI componentsapps/client/src/layers/entities/**/ui/**— entity UI componentsapps/client/src/layers/shared/ui/**— shared UI primitivesapps/client/src/dev/**— direct playground edits
After editing a UI component, ask yourself three questions:
- Is this component a good playground candidate? (See candidacy criteria below)
- Is it already in the playground? Check the section registries in
dev/sections/. - If it's already there, is the showcase still accurate? Does it reflect the current props, states, and visual appearance?
Candidacy Criteria
A component belongs in the playground if it meets any of these:
- Visual and reusable — renders UI that appears in more than one place, or could
- Has multiple meaningful states — loading, empty, error, active, disabled, etc.
- Part of the design system — buttons, inputs, cards, badges, overlays
- A composed widget or panel — TasksPanel, MessagingConnections, TunnelDialog, etc.
- Complex enough to regress — more than trivial markup; has conditional rendering, animations, or data-dependent layout
A component does NOT belong if it's:
- Pure logic (hooks, utilities, stores) with no visual output
- A one-line wrapper that adds a className
- A layout container with no meaningful visual states
- A page-level route component (the playground itself IS the page-level view)
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 Changed · +10 lines ac8f42055a2c
- 1mo ago Changed · +4 lines c95382c7a173
- 1mo ago First seen · 265 lines · 95 tokens per session scan A 52ed76721f00
maintaining-dev-playground is a skill published in the GitHub repository dork-labs/dorkos (12 stars, last pushed today), licensed MIT. It adds 95 tokens to every session and 4,022 once invoked, about $0.0004 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
design-system
Use when a ticket needs a systematic token + component foundation for a frontend — the three-layer token architecture (primitive → semantic → component), W3C DTCG design-token files, theming and dark mode, component specs with full state coverage, or a recommendation for which design system a product should have.…
frontend-foundations
Use on any frontend delivery to hold the surface-specific quality floor that engineering-craft doesn't cover — intentional visual hierarchy over template defaults, accessible-by-default markup, design tokens instead of hardcoded values, reusable components matching the repo, every state designed, and…
frontend-design
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
css-expert
CSS expert for flexbox, grid, animations, responsive design, and modern layout techniques.
scrollcraft
Premium scroll-driven landing pages; scroll = timeline.
scroll-craft
Build premium scroll-driven landing pages for service, product, food, and drink brands. Plan the visitor journey, page grammar, emotional peak, and bespoke signature move. Create dimensional heroes with independent visual planes, restrained motion, and separate mobile composition. Use supplied photos and footage or…