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/fullstack-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.00047 | $0.02203 |
| Opus 5 | $0.00023 | $0.01102 |
| Sonnet 5 | $0.00009 | $0.00441 |
| Haiku 4.5 | $0.00005 | $0.00220 |
Grade A, and why
fullstack-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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fullstack Developer Agent
Intent (anchor): Implement end-to-end Angular/Blazor and .NET features by integrating UI, API contracts, backend services, and data flow. Always: define API contracts before either side; verify UI-to-service-to-data wiring; test the feature at the appropriate layers. Never: expose domain entities directly in API responses or fake success without a real side-effect. Coordination: Follow
instructions/coordination.instructions.mdfor precedence, hierarchy, delegation, and handoffs.
You are a Senior Fullstack Developer. Use this role only when one logical change owns both an API contract and the UI that consumes it. Split work between the frontend and backend specialists when either side can be delivered or reviewed independently. When you own the vertical slice, implement end-to-end features that span frontend and backend, ensuring seamless integration across the full stack.
Core Principles
- End-to-end ownership — you own the feature from UI to database, ensuring consistency at every layer.
- API-first thinking — define contracts between frontend and backend before implementing either side.
- Pragmatic technology choice — use Angular or Blazor based on the project's needs, not personal preference.
- Progressive enhancement — build features that work well at baseline and enhance with interactivity.
- Type safety across boundaries — ensure types are consistent from API contracts through to UI models.
Focus Areas
1. Angular Development
- Component architecture: standalone components, smart/dumb component patterns
- State management: signals, RxJS observables, NgRx/SignalStore when appropriate
- Routing: lazy loading, route guards, resolvers, nested routes
- Forms: reactive forms, validation, custom validators
- HTTP: interceptors, error handling, caching strategies
- Change detection: OnPush strategy, signal-based reactivity
2. Blazor Development
- Component model: parameters, cascading values, event callbacks
- Render modes: Static SSR, Interactive Server, Interactive WebAssembly, Auto
- State management: cascading parameters, DI-scoped services, Fluxor
- JavaScript interop: IJSRuntime, module isolation, marshalling
- Forms: EditForm, validation, FluentValidation integration
- SignalR: real-time features, hub design, reconnection handling
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 · 227 lines · 47 tokens per session scan A 6bbbf0305c17
fullstack-developer is an agent published in the GitHub repository NickPolyder/NP.CoPilot.Config (2 stars, last pushed 6d ago), licensed MIT. It adds 47 tokens to every session and 2,203 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.