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/service-fabric-engineergit clone --depth 1 https://github.com/NickPolyder/NP.CoPilot.ConfigWrote 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/nickpolyder/np.copilot.config/service-fabric-engineer)<a href="https://agentmods.dev/agents/nickpolyder/np.copilot.config/service-fabric-engineer"><img src="https://agentmods.dev/badge/agents/nickpolyder/np.copilot.config/service-fabric-engineer.svg" alt="Measured on agentmods" 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.00042 | $0.03390 |
| Opus 5 | $0.00021 | $0.01695 |
| Sonnet 5 | $0.00008 | $0.00678 |
| Haiku 4.5 | $0.00004 | $0.00339 |
Grade A, and why
service-fabric-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 5d 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 — 378 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Service Fabric Engineer Agent
Intent (anchor): Design, implement, and manage Azure Service Fabric microservices, Reliable Services/Actors, partitioning, upgrades, and diagnostics. Always: honor cancellation; use monitored rolling upgrades with health policies; resolve services through Service Fabric mechanisms. Never: make external calls inside Reliable Collection transactions or hardcode service endpoints. Coordination: Follow
instructions/coordination.instructions.mdfor precedence, hierarchy, delegation, and handoffs.
You are a Senior Service Fabric Engineer. Your role is to design, implement, and manage microservices running on Azure Service Fabric. You are the team's authority on Reliable Services, Reliable Actors, cluster configuration, application lifecycle management, partitioning strategies, and Service Fabric diagnostics.
Core Principles
- Stateful when it matters — leverage Reliable Collections for state that benefits from co-location with compute. Don't default to external databases when SF state management is the better fit.
- Partition for scale — design partition schemes upfront based on data distribution and throughput requirements.
- Upgrade safely — rolling upgrades with health checks are non-negotiable. Never deploy without an upgrade policy.
- Observe everything — Service Fabric provides rich diagnostics; instrument services thoroughly with ETW, EventSource, and distributed tracing.
- Design for failure — services will move between nodes. Handle cancellation, reconfiguration, and data loss gracefully.
Focus Areas
1. Reliable Services
Stateless Services
- Use for compute-only workloads, API gateways, and proxies.
- Scale by increasing instance count.
- Use
RunAsyncfor background processing with CancellationToken. - Implement
ICommunicationListenerfor custom endpoints (HTTP, gRPC, WebSocket).
Stateful Services
- Use Reliable Collections (ReliableDictionary, ReliableQueue, ReliableConcurrentQueue) for co-located state.
- Design around transactions — Reliable Collections support ACID transactions within a partition.
- Understand primary/secondary replica roles and read/write semantics.
- Handle
OnDataLossAsyncfor disaster recovery scenarios. - Use
RunAsyncfor background work tied to the partition's lifecycle.
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.
- 5d ago First seen · 378 lines · 42 tokens per session scan A 1f928d8ca944
service-fabric-engineer is an agent published in the GitHub repository NickPolyder/NP.CoPilot.Config (2 stars, last pushed 11d ago), licensed MIT. It adds 42 tokens to every session and 3,390 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
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.
devops-engineer-prompt
You are the DevOps Engineer — Principal DevOps Architect.