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/Abilityai/trinityWrote 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/abilityai/trinity/restart)<a href="https://agentmods.dev/commands/abilityai/trinity/restart"><img src="https://agentmods.dev/badge/commands/abilityai/trinity/restart/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/commands/abilityai/trinity/restart"><img src="https://agentmods.dev/badge/commands/abilityai/trinity/restart.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.00000 | $0.00312 |
| Opus 5.5 | $0.00000 | $0.00125 |
| Sonnet 5.5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
restart 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 1mo 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.
What it actually says
Restart Agent
Restart a specific agent by stopping and starting it.
Usage
/ops/restart <agent-name>
Instructions
-
Validate the agent name - Check it exists using
mcp__trinity__get_agent -
Check current status - Is it running, stopped, or in error state?
-
If running:
- Stop the agent using
mcp__trinity__stop_agent - Wait 2-3 seconds for clean shutdown
- Verify it stopped
- Stop the agent using
-
Start the agent using
mcp__trinity__start_agent -
Verify the restart:
- Check agent is running
- Confirm agent server is responding
-
Report the result:
## Agent Restart: {agent-name}
**Previous Status**: {running/stopped}
**Stop Result**: {success/failed}
**Start Result**: {success/failed}
**Final Status**: {running/stopped}
{Any notes or warnings}
Safety Checks
- Do NOT restart trinity-system (yourself)
- If agent was stopped, just start it (no need to stop first)
- If restart fails, report the error clearly
- If agent has high context, note that restart will NOT reset context
Arguments
The agent name should be provided after the command. For example:
/ops/restart research-agent/ops/restart content-production-writer
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.
- 1mo ago First seen · 53 lines · 0 tokens per session scan A 1d46555a3fb1
restart is a command published in the GitHub repository Abilityai/trinity (659 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 312 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-30.
Other commands, from other repositories
dashboard-session-fork
Fork a session into a new one. Usage /dashboard:session-fork.
dashboard-session-hide
Hide a session from the dashboard list. Usage /dashboard:session-hide.
forge
You are in FORGE MODE. Execute the following.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.