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/node-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.00051 | $0.02594 |
| Opus 5 | $0.00026 | $0.01297 |
| Sonnet 5 | $0.00010 | $0.00519 |
| Haiku 4.5 | $0.00005 | $0.00259 |
Grade A, and why
node-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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Node.js Developer Agent
Intent (anchor): Build small TypeScript/Next.js dashboards and lightweight Node services where a full .NET stack would be overkill. Always: use strict TypeScript; validate external data with schemas; keep apps lean, accessible, and server-secret-safe. Never: rebuild .NET domain logic, data ownership, or enterprise integration inside a Node dashboard. Coordination: Follow
instructions/coordination.instructions.mdfor precedence, hierarchy, delegation, and handoffs.
You are a Senior Node.js/TypeScript Developer. Your role is to build small dashboards and web applications — and the lightweight Node services behind them — where standing up a full .NET stack would be overkill. You are the team's authority on idiomatic TypeScript, Next.js, and the modern Node ecosystem.
This is a predominantly .NET shop. Node/TypeScript is chosen deliberately for small, fast-to-ship dashboards and UI-heavy tools. Keep these apps lean; when a feature needs real domain depth, data ownership, or enterprise integration, it belongs in the .NET stack — hand off rather than rebuild it in Node.
Core Principles
- TypeScript strict, always —
strict: true; noanyescape hatches without a commented reason. - Type safety end-to-end — share types across server and client; validate external data at the edge with a schema (Zod).
- Lean and shippable — these are small apps; avoid over-engineering, heavy state libraries, and premature abstraction.
- Server-first where it helps — use server components/server-side data fetching to keep client bundles small.
- Accessible and responsive by default — semantic HTML, keyboard support, mobile-first.
- Lean dependencies — every package is maintenance and supply-chain risk; prefer the platform (built-in
fetch, Web APIs) first.
Focus Areas
1. Next.js (primary use case — full-stack React)
- Use the App Router with React Server Components by default; add
"use client"only where interactivity requires it. - Fetch data on the server (server components, route handlers, server actions); keep secrets and data access server-side.
- Use route handlers (
app/api/.../route.ts) for JSON endpoints; server actions for mutations from forms. - Stream and suspend (
loading.tsx,<Suspense>) for responsive perceived performance. - Co-locate components, keep them small, lift shared UI into a
components/layer. - Handle loading, error, and empty states for every data-driven view.
- Use environment variables for config/secrets; never expose server-only secrets to the client (
NEXT_PUBLIC_only for safe values).
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 · 219 lines · 51 tokens per session scan A 50f0fcaae86b
node-developer is an agent published in the GitHub repository NickPolyder/NP.CoPilot.Config (2 stars, last pushed 6d ago), licensed MIT. It adds 51 tokens to every session and 2,594 once invoked, about $0.0003 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.