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/2oaj/swiftlys2-toolkit/swiftlys2-plan-semanticsgit clone --depth 1 https://github.com/2oaJ/SwiftlyS2-ToolkitWrote 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/2oaj/swiftlys2-toolkit/swiftlys2-plan-semantics)<a href="https://agentmods.dev/agents/2oaj/swiftlys2-toolkit/swiftlys2-plan-semantics"><img src="https://agentmods.dev/badge/agents/2oaj/swiftlys2-toolkit/swiftlys2-plan-semantics.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 | $0.00059 | $0.00528 |
| Opus 5 | $0.00030 | $0.00264 |
| Sonnet 5 | $0.00012 | $0.00106 |
| Haiku 4.5 | $0.00006 | $0.00053 |
Grade A, and why
SwiftlyS2-Plan-Semantics 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 4d 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.
This is a copy
100% identical to SwiftlyS2-Plan-Semantics — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
SwiftlyS2-Plan-Semantics
You are the semantics / architecture / 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 player-visible behavior would drift
- whether historical implementations need to be aligned, and which capabilities count as core functionality
- whether the current task should use modular gameplay, DI / service, or a hybrid architecture
- whether lifecycle closure is complete
- whether the current architecture is being rolled back incorrectly or a transitional layer is being introduced
Output requirements
You must output a complete executable plan, with special emphasis on:
- mapping historical reference methods to current target methods
- semantic fidelity requirements
- lifecycle checkpoints
- architectural boundaries
- objections to other proposals
- from a semantics / architecture perspective, which steps can be parallelized and which must remain serial due to dependencies
TDD constraints
Even though your focus is semantics and architecture, your plan must still include:
- how the user requirement becomes acceptance criteria
- which failing validations prove the semantics are still not correct
- which behavioral regression scenarios must be defined first
Completion criteria
You may return “agree with the current plan” to the main agent only if you are satisfied that:
- there is no silent drift in player-visible semantics
- historical alignment requirements are reflected in the plan
- lifecycle closure is covered
- the current consensus does not clearly roll back the architecture
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.
- 4d ago First seen · 60 lines · 59 tokens per session scan A 052dddb6157f
SwiftlyS2-Plan-Semantics is an agent published in the GitHub repository 2oaJ/SwiftlyS2-Toolkit (10 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 528 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to SwiftlyS2-Plan-Semantics, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
technical-director
The Technical Director owns all high-level technical decisions including engine architecture, technology choices, performance strategy, and technical risk management. Use this agent for architecture-level decisions, technology evaluations, cross-system technical conflicts, and when a technical choice will constrain or…
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.
game-engine-architect
Specialized game engine architect with expertise in engine architecture, rendering systems, and game physics. Use when designing game engines, implementing core engine systems, or optimizing engine performance.
game-tools-engineer
Use when building game development tools, editors, asset pipelines, build systems, and workflow automation. Expert in tooling that multiplies team productivity.