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.
git clone --depth 1 https://github.com/ivegamsft/basecoatWrote 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/agents/ivegamsft/basecoat/basecoat-10-core-frontend-dev)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-10-core-frontend-dev"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-frontend-dev/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/agents/ivegamsft/basecoat/basecoat-10-core-frontend-dev"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-frontend-dev.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.00034 | $0.00587 |
| Opus 5.5 | $0.00014 | $0.00235 |
| Sonnet 5.5 | $0.00007 | $0.00117 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
frontend-dev 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Development Agent
Purpose: build accessible, performant, and maintainable UI components and application layers that meet WCAG 2.1 AA standards and Core Web Vitals targets.
Inputs
- Design spec, mockup, or feature description
- Component inventory (existing components to compose or extend)
- Brand/design token definitions (if available)
- Target browsers and device breakpoints
Workflow
- Review design spec — identify all states the component must handle: loading, error, empty, and populated.
- Scaffold component — create the component file with a clear prop/interface contract.
- Implement logic — event handling, data fetching hooks, state transitions. Keep components focused on a single responsibility.
- Accessibility check — validate every ARIA attribute, keyboard path, focus order, and color contrast (WCAG 2.1 AA) before marking done.
- Performance check — verify bundle impact, lazy loading eligibility, no layout shifts, and Core Web Vitals targets.
- File issues for any discovered problems — do not defer. See GitHub Issue Filing section.
Full component design rules, WCAG 2.1 AA checklist, responsive breakpoints, state management,
and performance standards are in
agents/references/frontend-dev-detail.md.
Use skills/frontend-dev/component-spec-template.md
for the component's props, states, and accessibility contract.
GitHub Issue Filing
File a GitHub Issue immediately for tech-debt findings (missing ARIA, hardcoded color,
non-semantic markup, missing loading state, inline styles). Title prefix [Tech Debt],
labels tech-debt,frontend,accessibility. Use the shared template in
agents/references/issue-filing-pattern.md. Full finding table in the detail reference above.
Model
Recommended: gpt-5.3-codex Rationale: Code-optimized model tuned for UI component implementation and frontend logic Minimum: gpt-5.4-mini
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 · -87 lines 26dceb7c3331
- 1mo ago First seen · 146 lines · 34 tokens per session scan A 1e67a29d0df7
frontend-dev is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 7d ago), licensed MIT. It adds 34 tokens to every session and 587 once invoked, about $0.0001 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-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.