command-service-template.cs

command-service-template.cs is a command for coding agents from 2oaJ/SwiftlyS2-Toolkit. It costs 0 tokens per session (480 once invoked), scanned A, original, MIT.

A C# template for a SwiftlyS2 service that owns the commands and hooks it registers. SwiftlyS2 is a toolkit in which plugins can add server commands, aliases, and chat-related hooks.

In plain words
What is it for?
Build a service with dependency injection, thread-safe command lifecycle management, stored identifiers, and install/uninstall logic for server or chat commands.
Why use it?
It keeps registration and cleanup in the same service, avoiding command handles being managed elsewhere. The pattern also supports starting, stopping, and conditionally installing commands safely.

Command

Install

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.

agentmods
npx agentmods add commands/2oaj/swiftlys2-toolkit/command-service-template.cs
Clone the repo
git clone --depth 1 https://github.com/2oaJ/SwiftlyS2-Toolkit

Wrote 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.

agentmods badge for command-service-template.cs

README.md
[![agentmods](https://agentmods.dev/badge/commands/2oaj/swiftlys2-toolkit/command-service-template.cs.svg)](https://agentmods.dev/commands/2oaj/swiftlys2-toolkit/command-service-template.cs)
Your own site
<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>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 480 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 4d ago against content hash ef3d6ef59e8a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

skills/SwiftlyS2-Toolkit/assets/development/commands/command-service-template.cs.md · 81 lines

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:

  • Commands
  • Dependency Injection
  • Thread 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 Guid values, 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 Guid values and reclaim them precisely in Uninstall()?
  • 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, and HookClientCommand?

Read the full file on GitHub · 81 lines

Changes

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.

  1. 4d ago First seen · 81 lines · 0 tokens per session scan A ef3d6ef59e8a

Subscribe to this mod's changes

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.