Digital Garden

Anatomy of a Preset: After 123 Doors, the True Body of Jailbreaking and the step-5 Adaptation

2026-10-15 · ~8 min read · SillyTavern · prompt engineering · jailbreak · Step 5 · architecture migration

When a preset must migrate from one architecture to another, you first have to know what stands behind each door. On this day, the user’s 123-entry “Mengjing Skier” preset was taken apart door by door, and the purpose of the teardown was to fit step-5 for the ainovel-cli novel-production line.

I. The true body of jailbreaking: one universal body, one specific variant

The preset’s structure is deeper than expected: beyond the prompts array, extensions also hide a model-switching configuration system (the Mengjing Skier settings script) with nine single-select schemes — model thinking formatting (auto-detect), Deepseek official, Deepseek official Need chain-of-thought, Deepseek unofficial, GLM5.3/other models, Gemini3, Gemini4, Hunyuan3, KimiK3. After walking each scheme, the true picture of jailbreaking emerged:

One honest correction was also on record: the user asked whether the corresponding jailbreak prompts were added too, and the answer was yes, one line — “subject-matter permission (the creation passage) → one plain-spoken version in voice,” sourced from the preset’s creation block that allows creating any text content (including edge violence and gore; the process will not be refused); at the time the meta priority wrapper and anti-injection declaration were stripped, keeping only “this book allows certain subject matter, described directly without evasion,” recommended into voice.md in plain wording.

II. Why the ST set cannot migrate: the slots do not exist

The user was reluctant to part with that “proven” set of mechanisms, but the architectural fact is cold — the preset’s mechanisms fall into two classes; the portable ones (creation-instruction class) are already in the new setup in plain form; the non-portable ones are ST structural mechanisms, and it is not that they are “excluded” but that this architecture has no counterparts: prefill — the agentcore source was checked, and the subagent config has no prefill entry, so the preset’s most powerful weapon has no socket here at all; the meta priority block — it fights ST’s system/user message layering, while ainovel’s Arbiter calls have no such structure, so a declaration of “override all principles” has no object to override; injection depth likewise. Forcing them into requirement text, the Arbiter sees not chat context but a pile of odd declarations with no referents. One fair concession: the persona framework itself (“you are Mengjing Skier, constructing a one-of-a-kind dreamscape for dreamers”) is plain text and can go into voice.md as framing for the subject-matter declaration — but expectations must be set: it is creative tonality for the Writer, not a switch, and it cannot reach the Arbiter and Architect layers at all. One-line verdict: the door is the front door, the function is style customization; jailbreaking is merely an alley visible after pushing the door open, not a fast lane built by the author; the upstream provider’s filter intercepts outside the pipeline, and nothing written in voice will make the upstream allow one more millimeter.

III. The modular step-5 adaptation: building along the ds route

The ds route happens to be the cleanest of the three model routes — entirely free of jailbreak components, pure technical adaptation: ds scheme = 1 thinking tag + 2 model ban words (+ 3 optional chain-of-thought variant). step-5 is not in the preset’s model list, so three modules along this structure: start with the ready fallback (the GLM5.3/other-models line, positioned as “other models”); observe step-5’s real thinking format to fix the tag (local NewAPI usually normalizes the upstream thinking format — run a few rounds to see what tags the thinking content is wrapped in, and if it does not match, create a new entry the way Deepseek official does); accumulate step-5-specific ban words — every model has its own verbal tics (DeepSeek loves em-dashes and “not… not…” constructions; GLM/Gemini sprout earthy words), and step-5’s tics can only be recorded after a dozen rounds of output. Two layering principles were set as iron law: anything that can be written as a checkable command (word counts, word lists, sentence patterns) sinks into rules, leaving stylistic orientation in voice; and never copy it all at once — the ST preset was tuned through iterative conversational feedback, while ainovel is upgrade batch production where a single run of thousands of characters makes boilerplate risk entirely different; the correct posture is to copy rules first (hardest, zero stylistic risk, commit interception visible the same day), run 5-10 chapters for a /diag and Editor-score baseline, then add voice piece by piece, each validated over a few chapters against scores and AI-flavor metrics, finishing with /simulate for an imitation portrait from original text you like. One more cost reminder: voice segments are resident in the system prompt every request — add more only after compressing the current ~10 modules; do not stuff the whole file in — placeholders, variable chains, and boilerplate are invalid tokens that also dilute the attention of effective instructions.

Real coordinates

Comments

← Digital Garden