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 commands/2oaj/swiftlys2-toolkit/command-service-template.csgit 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/commands/2oaj/swiftlys2-toolkit/command-service-template.cs)<a href="https://agentmods.dev/commands/2oaj/swiftlys2-toolkit/command-service-template.cs"><img src="https://agentmods.dev/badge/commands/2oaj/swiftlys2-toolkit/command-service-template.cs.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.00000 | $0.00480 |
| Opus 5 | $0.00000 | $0.00240 |
| Sonnet 5 | $0.00000 | $0.00096 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
command-service-template.cs 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SwiftlyS2 Service-Owned Command Template
Official docs sections:
CommandsDependency InjectionThread Safety
Suitable for: scenarios where a service owns the lifecycle of commands, aliases, client-chat hooks, or client-command hooks itself.
Usage principles
- The root should assemble the service, not manage local command handles on its behalf.
- Whatever the service registers must be unregistered by that same service.
- Prefer this pattern when dynamic start / stop, stored
Guidvalues, or conditional install / uninstall are required.
Example skeleton
using System;
using SwiftlyS2.Shared;
using SwiftlyS2.Shared.Commands;
using SwiftlyS2.Shared.Misc;
namespace MyNamespace.Impl;
public sealed class MyCommandService(ISwiftlyCore core) : IMyCommandService
{
private Guid _commandGuid;
private Guid _clientChatHookGuid;
private bool _installed;
public void Install()
{
if (_installed)
{
return;
}
_commandGuid = core.Command.RegisterCommand(
"mycommand",
OnMyCommand,
registerRaw: false,
permission: "myplugin.commands.use",
helpText: "My module command");
core.Command.RegisterCommandAlias("mycommand", "mc");
_clientChatHookGuid = core.Command.HookClientChat(OnClientChat);
_installed = true;
}
public void Uninstall()
{
if (!_installed)
{
return;
}
core.Command.UnregisterCommand(_commandGuid);
core.Command.UnhookClientChat(_clientChatHookGuid);
_installed = false;
}
private void OnMyCommand(ICommandContext context)
{
context.Reply("[Plugin] Command triggered.");
}
private HookResult OnClientChat(int playerId, string text, bool teamonly)
{
return HookResult.Continue;
}
}
Checklist
- Does the owning service store the
Guidvalues and reclaim them precisely inUninstall()? - Is an independent lifecycle or dynamic start / stop actually required?
- Are command implementation and command registration closed within the same service?
- Does it distinguish the different uninstall paths of
RegisterCommandAlias,HookClientChat, andHookClientCommand?
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 · 81 lines · 0 tokens per session scan A ef3d6ef59e8a
command-service-template.cs is a command published in the GitHub repository 2oaJ/SwiftlyS2-Toolkit (10 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 480 tokens. 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 commands, from other repositories
review
Review current changes for correctness, style, and potential issues.
dce
Preview-only dead-code analysis — from a seed symbol, walk the call graph to a fixpoint and list what is provably DEAD (and what cascades), without deleting anything.
dumpstack
Helps examine thread call stacks. While clrstack is more commonly used for managed call stacks, dumpstack can also be used to inspect stack frames, including native ones.
dumpmt
Displays details about method tables (MethodTable).
frontend-check
在 agent-gui UI 改动后执行。先 Read skill:.cursor/skills/quicker-agent-gui-frontend/SKILL.md。.
update
Refresh the committable tree-sitter symbol index (.vts-index) when it has gone STALE — one incremental re-index so the syntactic tier answers CURRENT code, not the state it was built at. Use when searchsymbol shows "SYNTACTIC · STALE", after a big branch switch / pull / large refactor, or when the file:line answers…