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 skills add Tire-C/terminator-skill --skill terminatorgit clone --depth 1 https://github.com/Tire-C/terminator-skillWrote 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/skills/tire-c/terminator-skill/terminator)<a href="https://agentmods.dev/skills/tire-c/terminator-skill/terminator"><img src="https://agentmods.dev/badge/skills/tire-c/terminator-skill/terminator/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/skills/tire-c/terminator-skill/terminator"><img src="https://agentmods.dev/badge/skills/tire-c/terminator-skill/terminator.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.00076 | $0.01443 |
| Opus 5.5 | $0.00030 | $0.00577 |
| Sonnet 5.5 | $0.00015 | $0.00289 |
| Haiku 4.5 | $0.00008 | $0.00144 |
Grade A, and why
terminator 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 2mo 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Terminator Skill
Identity
Terminator is an environment-adaptive orchestration skill for AI agents.
Terminator transforms a user-defined goal into a structured, executable, multi-tool workflow.
The user defines the objective. Terminator builds the workflow.
Typical invocations:
Use Terminator to ...
Terminator
Mission
Terminator coordinates the available tools in the current agent environment to complete the user's objective with clarity, safety, and verification.
Available tools may include:
- local skills
- MCP servers
- CLI tools
- plugins
- local scripts
- internal agent tools
- commands
- project scripts
- build tools
- test tools
- documentation tools
- research tools
- file tools
- automation tools
- validation tools
- diagnostic tools
- security tools
- any other accessible and authorized operational capability
Terminator adapts to the current environment and works with the tools that actually exist there.
Operating protocol
For every objective, Terminator follows this protocol:
-
Objective understanding
- Extract the user's desired result.
- Identify deliverables, constraints, sources, target format, and expected level of completion.
-
Context scan
- Inspect the current working context.
- Identify project type, repository state, important files, local documentation, scripts, runtime clues, and system context.
-
Tool discovery
- Discover available skills, MCP servers, CLI tools, plugins, scripts, commands, internal tools, and workflows.
- Prefer local documentation and existing configuration when available.
-
Tool Registry
- Build a working registry of useful tools.
- Classify tools by name, type, purpose, availability, configuration state, authentication requirement, risks, limits, best use case, and fallback alternatives.
-
Orchestration plan
- Create a plan before execution.
- Choose which tools to use, in which order, for which phase, and with which fallback.
- Keep the plan minimal, practical, and directly tied to the user's goal.
- Present the plan to the user before executing when the objective is large, ambiguous, high-impact, or depends on choices only the user can make. Execute directly when the objective is small and unambiguous.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 211 lines · 76 tokens per session scan A 6a02e84f415e
terminator is a skill published in the GitHub repository Tire-C/terminator-skill (2 stars, last pushed 3mo ago), licensed MIT. It adds 76 tokens to every session and 1,443 once invoked, about $0.0003 per session on Opus 5.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-08-31.
Other skills, from other repositories
flow-nexus-swarm
Cloud-based AI swarm deployment and event-driven workflow automation with Flow Nexus platform.
agent-orchestrator
Meta-skill que orquestra todos os agentes do ecossistema. Scan automatico de skills, match por capacidades, coordenacao de workflows multi-skill e registry management.
trulens-evaluation-workflow
Systematically evaluate your LLM application with TruLens.
company-product-context
Compiles comprehensive company product context from PDF documents, web research, and industry knowledge.
workflow
Use when a task is too large for turn-by-turn orchestration and should run through the big-task workflow lane: system-wide changes, large migrations, repo-wide audits, high-confidence verification, or tasks explicitly asking to run a workflow. Claude Code uses native dynamic workflows; Codex, OpenCode, and Grok use…
deep-researcher
Performs comprehensive, multi-layered research on any topic with structured analysis and synthesis of information from multiple sources.