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 design-patternsgit 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/design-patterns)<a href="https://agentmods.dev/skills/mdmatk/tormentnexus/design-patterns"><img src="https://agentmods.dev/badge/skills/mdmatk/tormentnexus/design-patterns/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/design-patterns"><img src="https://agentmods.dev/badge/skills/mdmatk/tormentnexus/design-patterns.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.00042 | $0.01812 |
| Opus 5.5 | $0.00017 | $0.00725 |
| Sonnet 5.5 | $0.00008 | $0.00362 |
| Haiku 4.5 | $0.00004 | $0.00181 |
Grade A, and why
design-patterns 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
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 249 lines · 42 tokens per session scan A 5618acc51803
design-patterns is a skill published in the GitHub repository MDMAtk/TormentNexus (12 stars, last pushed yesterday), licensed AGPL-3.0. It adds 42 tokens to every session and 1,812 once invoked, about $0.0002 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
bevy-ecs-patterns
Use when writing Bevy (Rust ECS) game code - pin and respect the repo's minor version, plugins/systems/queries/resources, schedules with FixedUpdate and Time, states and run conditions, messages vs observers across versions, required components, testing systems with App::update and a manual time strategy, compile-time…
rust-axum-service
Use when building or extending a Rust service - axum on tokio (or the repository's actix-web / rocket), typed errors with IntoResponse, serde at the boundary, sqlx queries and migrations, never blocking the runtime, tracing, clippy.
sruja-project
Procedural workflows for working with the Sruja codebase. Teaches AI editors how to add components, validate changes, and follow patterns.
language-rust
Rust idioms — ownership, lifetimes, and iterators. Auto-load when working with .rs files, Cargo.toml, or when the user mentions Rust, cargo, ownership, borrow checker, lifetime, or async Rust.
rust-core
Rust implementation guidance — stack-specific. Covers project structure, idiomatic patterns, ownership, error handling, testing, security, and observability for Rust backend services and CLIs. Use when the user asks about Rust-specific patterns, ownership, async with Tokio, testing strategy, or production reliability.…
python-di-soa-patterns
DI/SOA decision tree with full code examples for Python architecture decisions.