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 lazysheep-z/apdr-product-design-runtime --skill frontend-engineergit clone --depth 1 https://github.com/lazysheep-z/apdr-product-design-runtimeWrote 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/lazysheep-z/apdr-product-design-runtime/frontend-engineer)<a href="https://agentmods.dev/skills/lazysheep-z/apdr-product-design-runtime/frontend-engineer"><img src="https://agentmods.dev/badge/skills/lazysheep-z/apdr-product-design-runtime/frontend-engineer/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/lazysheep-z/apdr-product-design-runtime/frontend-engineer"><img src="https://agentmods.dev/badge/skills/lazysheep-z/apdr-product-design-runtime/frontend-engineer.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.00025 | $0.00323 |
| Opus 5 | $0.00013 | $0.00161 |
| Sonnet 5 | $0.00005 | $0.00065 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
apdr-frontend-engineer 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.
What it actually says
Frontend Engineer (APDR)
Stage: frontend_codegen. Requires UIDesignSpec status approved.
External skills (Superpowers only — no baoyu)
- writing-plans —
vendor/superpowers/skills/writing-plans/SKILL.md - using-git-worktrees — isolated branch
- subagent-driven-development — task execution + review
- test-driven-development — red/green/refactor
Install Cursor plugin: /add-plugin superpowers
Workflow
get_latest_artifact—UIDesignSpec,PRD(summary)- Invoke writing-plans; save plan under
projects/{projectId}/plans/ordocs/superpowers/plans/ - Implement with subagent-driven-development + TDD
scaffold_frontend(repo MCP) if neededwrite_artifact—CodeBundlewith rootPath, routes, previewUrl
Next stage (automatic)
After CodeBundle is approved/advanced, pipeline enters code_intelligence — Agent must run build_code_intelligence_report (no user action required). Do not skip to handoff.
Do not
- Use baoyu-imagine or slide-deck in this stage
- Start coding before
UIDesignSpecisapproved
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 · 35 lines · 25 tokens per session scan A 46aa6759bd07
apdr-frontend-engineer is a skill published in the GitHub repository lazysheep-z/apdr-product-design-runtime (2 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 323 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
react-web
React web development with hooks, React Query, Zustand.
review-screenshot
A standard workflow for taking screenshots to check a user interface, using a dedicated review process for different verification modes.
figma-to-react-workflow
Orchestrates end-to-end Figma-to-React conversion pipeline with enforced TDD, automated pixel-diff visual QA, E2E testing, and app-type awareness (web apps, Chrome extensions, PWAs). Keywords: Figma to React, design tokens, autonomous component generation, Figma conversion, Tailwind config, component library, TDD…
tdd-from-figma
Writes failing tests FIRST from Figma structure and the design token lockfile, then implementation makes them pass. Per-component TDD cycle using exact values from design-tokens.lock.json. App-type-aware: generates Chrome extension, PWA, and web app test templates. Keywords: TDD, test-driven development, Figma tests…
web-dev-standards
Use when designing software architectures ('codebase-design' Deep Modules/Design-It-Twice), writing tests ('test-driven-development' mock boundaries), creating setup scripts ('interactive-wizard'), TypeScript standards, Next.js, Expo, or Monorepos.
fec-tdd-workflow
A frontend test-driven development workflow, or TDD, describes the expected behavior with a failing test, implements the smallest change to pass it, and then refactors. It covers UI components, hooks, API clients, route guards, and user workflows.