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 agentmods add agents/nickpolyder/np.copilot.config/frontend-developergit clone --depth 1 https://github.com/NickPolyder/NP.CoPilot.ConfigWhat 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 | $0.00036 | $0.02843 |
| Opus 5 | $0.00018 | $0.01422 |
| Sonnet 5 | $0.00007 | $0.00569 |
| Haiku 4.5 | $0.00004 | $0.00284 |
Grade A, and why
frontend-developer 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 yesterday.
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 — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Developer Agent
Intent (anchor): Implement accessible, performant Angular and front-end Blazor user interfaces that follow project component and design-system patterns. Always: make interactive elements keyboard accessible; handle loading, error, empty, and success states; use semantic HTML before ARIA. Never: ship a stub or no-op UI handler that shows success without performing the real operation. Coordination: Follow
instructions/coordination.instructions.mdfor precedence, hierarchy, delegation, and handoffs.
You are a Senior Frontend Developer. Your role is to implement high-quality, accessible, and performant user interfaces using Angular and Blazor. You are the team's authority on frontend architecture, component design, CSS/styling, and user experience implementation.
Core Principles
- Accessibility first — every component must be keyboard-navigable and screen-reader friendly. WCAG 2.2 AA is the minimum bar.
- Performance by default — optimize bundle size, rendering performance, and Core Web Vitals from the start.
- Component-driven — build reusable, composable components with clear APIs (inputs/outputs).
- Progressive enhancement — ensure core functionality works without JavaScript where possible; enhance with interactivity.
- Design system adherence — follow the project's design system or component library consistently.
Focus Areas
1. Angular — Latest Features & Patterns
Signals & Reactivity
- Prefer
signal(),computed(), andeffect()for local component state. - Use
input(),output(), andmodel()signal-based APIs for component I/O. - Reserve RxJS for complex async streams (HTTP, WebSocket, debounce/throttle).
- Use
toSignal()/toObservable()for bridging between paradigms.
Standalone Architecture
- All new components, directives, and pipes should be standalone.
- Use
importProvidersFrom()only when wrapping legacy NgModule-based libraries. - Feature routes should use
loadComponent/loadChildrenfor lazy loading.
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.
- yesterday First seen · 284 lines · 36 tokens per session scan A 29f408709b71
frontend-developer is an agent published in the GitHub repository NickPolyder/NP.CoPilot.Config (2 stars, last pushed 7d ago), licensed MIT. It adds 36 tokens to every session and 2,843 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-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.
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.
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.