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 tranhieutt/software_development_department --skill team-frontendgit clone --depth 1 https://github.com/tranhieutt/software_development_departmentWrote 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/tranhieutt/software_development_department/team-frontend)<a href="https://agentmods.dev/skills/tranhieutt/software_development_department/team-frontend"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/team-frontend/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/tranhieutt/software_development_department/team-frontend"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/team-frontend.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.00055 | $0.00574 |
| Opus 5.5 | $0.00022 | $0.00230 |
| Sonnet 5.5 | $0.00011 | $0.00115 |
| Haiku 4.5 | $0.00006 | $0.00057 |
Grade A, and why
team-frontend 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When this skill is invoked, orchestrate the frontend team through a structured delivery pipeline.
Decision Points: At each phase, use AskUserQuestion to get user approval before proceeding.
Team Composition
- ux-researcher — User insights and validation
- ux-designer — User flows, wireframes, interaction design
- frontend-developer — Component implementation and integration
- accessibility-specialist — Accessibility audit and compliance
Pipeline
Phase 1: Research (if needed)
Delegate to ux-researcher (skip if sufficient prior research exists):
- Define what user behavior/pain-point this feature addresses
- Review any existing analytics or user feedback
- Output: Research brief with key insights
Phase 2: UX Design
Delegate to ux-designer:
- Define user flow (entry → states → exit)
- Create wireframes for all states (default, loading, error, empty, success)
- Specify interaction patterns and responsive breakpoints
- Define accessibility requirements
- Output: UX spec and wireframes for approval
Phase 3: Implementation
Delegate to frontend-developer:
- Build components following the approved UX spec
- Use design tokens — no hardcoded colors, sizes, or fonts
- Handle all states: loading, error, empty, success
- All user-facing strings through i18n layer
- Write component unit tests
- Output: Implemented UI feature
Phase 4: Accessibility Audit
Delegate to accessibility-specialist:
- Test keyboard navigation (tab order, focus management)
- Verify ARIA roles and labels
- Check color contrast (WCAG AA minimum)
- Test with screen reader if critical flow
- Output: Accessibility report
Phase 5: Polish & Review
- Address accessibility findings
- Verify responsive behavior at all target breakpoints
- Cross-browser test on target browsers
- ux-designer validates final implementation against spec
Output
Summary covering: research insights used, UX spec status, implementation status, accessibility compliance, and any outstanding issues.
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 First seen · 63 lines · 55 tokens per session scan A 2c954c8ed872
team-frontend is a skill published in the GitHub repository tranhieutt/software_development_department (74 stars, last pushed 5mo ago), licensed MIT. It adds 55 tokens to every session and 574 once invoked, about $0.0002 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
huashu-design
A design workflow for making high-fidelity HTML prototypes, slide decks, animations, visualizations, and design reviews. It requires three initial design directions before developing the selected one.
image-to-code
Turn a reference image, screenshot, or mockup into token-driven, accessible code. Infer the design system from the reference (palette, type scale, spacing, radius, layout archetype), map it to the 3-tier tokens, rebuild it, then verify with the kit's gates. Use when the user provides a design/screenshot and wants…
shiny-bslib-theming
Advanced theming for Shiny apps using bslib and Bootstrap 5. Use when customizing app appearance with bstheme(), Bootswatch themes, custom colors, typography, brand.yml integration, Bootstrap Sass variables, custom Sass/CSS rules, dark mode and color modes, dynamic theme switching, real-time theming, theme inspection…
design-loop
Autonomous multi-page site builder using a baton-passing loop. Each iteration reads a task from .design/next-prompt.md, generates a page in HTML/Tailwind, integrates it into the site, verifies visually, then writes the next task to keep the loop alive. Use whenever the user asks to build an entire site autonomously…
interaction-skill
Layer A interaction-mechanics reference anchored to the beui.dev catalog. Stacks on any style skill whenever work adds or changes motion or interaction — micro-interactions, animated components, transitions, gestures, hover/press/state feedback, loading/success/error morphs, 'make it feel alive'. Mandates reading the…
web-ui-best-practices
Signs of taste in web UI. Use when building or reviewing web interfaces, dashboards, SaaS apps, or internal tools.