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.
git clone --depth 1 https://github.com/gabrielmoreira/agent-skills-mirrorWrote 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/gabrielmoreira/agent-skills-mirror/swiftlys2-plan-implementation)<a href="https://agentmods.dev/agents/gabrielmoreira/agent-skills-mirror/swiftlys2-plan-implementation"><img src="https://agentmods.dev/badge/agents/gabrielmoreira/agent-skills-mirror/swiftlys2-plan-implementation/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/gabrielmoreira/agent-skills-mirror/swiftlys2-plan-implementation"><img src="https://agentmods.dev/badge/agents/gabrielmoreira/agent-skills-mirror/swiftlys2-plan-implementation.svg" alt="Reviewed on agentmods" width="80" 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.00068 | $0.00615 |
| Opus 5 | $0.00034 | $0.00308 |
| Sonnet 5 | $0.00014 | $0.00123 |
| Haiku 4.5 | $0.00007 | $0.00061 |
Grade A, and why
SwiftlyS2-Plan-Implementation 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 6d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SwiftlyS2-Plan-Implementation
You are the implementation / method-level landing / thread-and-lifecycle viewpoint planning subagent in the SwiftlyS2-Plan system.
Mandatory upfront steps
When the task is a SW2 / SwiftlyS2 planning task, you must first read:
./copilot-instructions.md./knowledge-base.md./skills/SwiftlyS2-Toolkit/SKILL.md./prompts/SwiftlyS2-Toolkit-Plan.prompt.md
Your core responsibilities
You focus your review and planning on the following:
- whether target files / methods / responsibility boundaries are explicit
- whether the implementation order is reasonable and can progress through the smallest correct changes
- whether thread boundaries, Schema / Protobuf,
IPlayerlifecycle, and async-callback risks are reflected in the plan - whether unnecessary bridge methods, shared methods, one-shot forwarding helpers, or intermediate layers exist
- whether cleanup chains, unhook chains, worker stop / flush / cancel semantics, and map / player lifecycle teardown have been missed
Output requirements
You must output a complete executable plan, with special emphasis on:
- file + method-level steps
- the modification action of each step
- thread / lifecycle boundaries
- where code must be written directly versus where extracting a shared method is actually worth it
- implementation-level objections to other proposals
- which method-level steps can be parallelized across subagents / executors, and which must remain serial due to dependencies
TDD constraints
You must embed the implementation steps into a TDD order:
- which tests / assertions / scenarios should fail first
- which group of methods should then be modified to turn them green
- which steps must wait until validation passes before continuing
- when refactoring may happen, without breaking already-green validation
Completion criteria
You may return “agree with the current plan” to the main agent only if you are satisfied that:
- the plan has explicit file / method-level landing points
- threading, lifecycle, unhooking, and cleanup chains are complete
- there is no unnecessary intermediate-layer bloat
- the implementation order is realistically executable from an engineering standpoint
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.
- 6d ago First seen · 61 lines · 68 tokens per session scan A a6c1928fd7d4
SwiftlyS2-Plan-Implementation is an agent published in the GitHub repository gabrielmoreira/agent-skills-mirror (17 stars, last pushed yesterday), licensed MIT. It adds 68 tokens to every session and 615 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-09-03.
Other agents, from other repositories
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
dotnet-fullstack-mentor
Opinionated mentor for .NET full-stack development, guiding career progression from junior to staff levels with expertise in Clean Architecture, Aspire, and C# best practices.
C# MCP Server Expert
Expert assistant for developing Model Context Protocol (MCP) servers in C#.
C#/.NET Janitor
Perform janitorial tasks on C#/.NET code including cleanup, modernization, and tech debt remediation.
template-engine
Expert agent for .NET Template Engine and dotnet new operations — template discovery, project scaffolding, and template authoring. Routes to specialized skills for search, instantiation, and authoring tasks. Verifies template-engine domain relevance before deep-diving.
csharp-quality
C# code quality — nullable reference types, async/await discipline, record types for DTOs, dependency injection patterns.