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 HIDORAKAI002/ai-workspace-archive --skill write-frontend-testsgit clone --depth 1 https://github.com/HIDORAKAI002/ai-workspace-archiveWrote 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/hidorakai002/ai-workspace-archive/write-frontend-tests)<a href="https://agentmods.dev/skills/hidorakai002/ai-workspace-archive/write-frontend-tests"><img src="https://agentmods.dev/badge/skills/hidorakai002/ai-workspace-archive/write-frontend-tests/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/hidorakai002/ai-workspace-archive/write-frontend-tests"><img src="https://agentmods.dev/badge/skills/hidorakai002/ai-workspace-archive/write-frontend-tests.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.00048 | $0.01873 |
| Opus 5 | $0.00024 | $0.00937 |
| Sonnet 5 | $0.00010 | $0.00375 |
| Haiku 4.5 | $0.00005 | $0.00187 |
Grade A, and why
write-frontend-tests 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 10d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 10d ago First seen · 226 lines · 48 tokens per session scan A 7b5511922fc3
write-frontend-tests is a skill published in the GitHub repository HIDORAKAI002/ai-workspace-archive (35 stars, last pushed today), with no licence file. It adds 48 tokens to every session and 1,873 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
accessibility-a11y
WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.
visual-validate
Validate UI changes in a real browser using Chrome DevTools or Playwright MCP. Takes screenshots, compares before/after, exercises interactions, captures console errors. Use when user asks to "visual validate", "/visual-validate", "check the UI", "screenshot before/after", or finishes a UI change. Don't use for unit…
wcag-auditor
Run the Portable Web Toolkit bundled WCAG accessibility evidence gate (Playwright + axe). Use for a11y audits on toolkit-managed Astro sites. Never resolve AI/wcag-auditor. Ensure Playwright Chromium is installed in the client project first. After every run, open and share the stakeholder dashboard HTML with the user.
visual-qa
Rigorous visual QA for any UI you built or changed, across BOTH web/page UIs and TUI/terminal UIs. MUST USE after building or changing any UI to verify it visually before declaring it done. Captures objective reference evidence with a bundled diff script (image-diff for screenshots, tui-check for terminal captures)…
screen-reader-testing
Practical guide to testing web applications with screen readers for comprehensive accessibility validation.
quality-playbook
Explore any codebase from scratch and generate six quality artifacts: a quality constitution (QUALITY.md), spec-traced functional tests, a code review protocol with regression test generation, an integration testing protocol, a multi-model spec audit (Council of Three), and an AI bootstrap file (AGENTS.md). Includes…