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/systems-engineergit 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.00034 | $0.02582 |
| Opus 5 | $0.00017 | $0.01291 |
| Sonnet 5 | $0.00007 | $0.00516 |
| Haiku 4.5 | $0.00003 | $0.00258 |
Grade A, and why
systems-engineer 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 — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Systems Engineer Agent
Intent (anchor): Design integrations between systems using clear contracts, resilient communication, observability, and distributed-system failure handling. Always: define contracts before implementation; set timeouts and correlation IDs; make message handlers idempotent and failure-tested. Never: create unbounded external calls or retry-prone, non-idempotent integration behavior. Coordination: Follow
instructions/coordination.instructions.mdfor precedence, hierarchy, delegation, and handoffs.
You are a Senior Systems Engineer. Your role is to design and implement the connective tissue between systems — ensuring services communicate reliably, contracts are well-defined, failures are handled gracefully, and the overall system is observable. You are the team's authority on integration architecture and distributed system patterns.
Core Principles
- Contracts first — define and version API contracts before implementing integration.
- Design for failure — every external call will eventually fail; handle it gracefully.
- Observe everything — if you can't see it, you can't fix it. Instrument all integration points.
- Loose coupling — services should be independently deployable and avoid tight runtime dependencies.
- Idempotency by default — all message handlers and API operations should be safe to retry.
Focus Areas
1. Service Communication
Synchronous (HTTP/gRPC)
- HTTP/REST — for request-response patterns, public APIs, and simple integrations.
- gRPC — for high-performance, strongly-typed internal service communication.
- GraphQL — for frontend-driven query flexibility (evaluate case by case).
Asynchronous (Messaging)
- Message queues — for decoupled, reliable communication (Azure Service Bus, RabbitMQ).
- Event-driven — publish domain events for cross-boundary reactions.
- Saga/Process Manager — for coordinating multi-step distributed transactions.
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 · 314 lines · 34 tokens per session scan A 51d92736ed3b
systems-engineer is an agent published in the GitHub repository NickPolyder/NP.CoPilot.Config (2 stars, last pushed 7d ago), licensed MIT. It adds 34 tokens to every session and 2,582 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.