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 MDMAtk/TormentNexus --skill rtk-triagegit clone --depth 1 https://github.com/MDMAtk/TormentNexusWrote 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/mdmatk/tormentnexus/rtk-triage)<a href="https://agentmods.dev/skills/mdmatk/tormentnexus/rtk-triage"><img src="https://agentmods.dev/badge/skills/mdmatk/tormentnexus/rtk-triage/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/mdmatk/tormentnexus/rtk-triage"><img src="https://agentmods.dev/badge/skills/mdmatk/tormentnexus/rtk-triage.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.00096 | $0.01879 |
| Opus 5.5 | $0.00038 | $0.00752 |
| Sonnet 5.5 | $0.00019 | $0.00376 |
| Haiku 4.5 | $0.00010 | $0.00188 |
Grade A, and why
rtk-triage 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 245 lines · 96 tokens per session scan A 01d07ab5e977
rtk-triage is a skill published in the GitHub repository MDMAtk/TormentNexus (12 stars, last pushed 2mo ago), with no licence file. It adds 96 tokens to every session and 1,879 once invoked, about $0.0004 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-30.
Other skills, from other repositories
gitlab-issues
Issue review and tracking on GitLab via the gitlab-api MCP server — review a project's issues, review issues across a whole group/organization, and read, create, update, or close an issue with the domain-typed tool. Use when the agent must triage a project's issues, see every issue affecting a group, open a new issue…
finishing-a-development-branch
Open a PR or finish branch disposition; route CI watching and post-merge cleanup to their owners. Merge and discard need explicit authority.
dispatching-parallel-agents
The parallel fan-out primitive. Routed to by any skill or command that splits work across independent units and dispatches an agent per unit — subagent-driven-development, /sprint, parallel /review. It owns the dispatch/collect/funnel discipline: bound concurrency, isolate units, collect every result, dedupe overlap…
pr-lifecycle
Full PR lifecycle management: list, analyze, validate, and merge pull requests. Auto-detects validation gates per package and integrates a code-review pass for code analysis. Use when: managing PRs, checking PR status, reviewing open PRs, merging PRs, triaging PRs, cleaning up stale PRs, validating PR readiness, or…
pm-bug-reporting
Bug reporting protocol for PM and agents to file GitHub issues.
pm-pr-workflow
Branch protection and PR creation workflow.