| name | poison-mask |
| description | Use Poison Mask when the right move is not to poison one tile on the floor but to contaminate a specific interface, workflow surface, or operating persona that the target keeps wearing. Poison Mask attaches the cost to continued contact: every repeated use of the same channel, wrapper, queue, ritual, or decision surface becomes more unpleasant, slower, riskier, or more draining. Unlike Poison Face, which punishes staying in one place, Poison Mask punishes continuing to operate through one poisoned surface. Unlike Time Bomb, it is not waiting to go off later; unlike Killer Eye, it is not there to detect passage; unlike Anti Damage, it is proactive rather than retaliatory. |
| version | 0.1.0 |
| author | mmbnchips |
| license | CC0-1.0 |
| compatibility | Hermes Agent skills system |
| metadata | {"hermes":{"tags":["shipping-now","hybrid","control-and-terrain","control","terrain","positioning","room-control"],"homepage":"https://github.com/Hmbown/mmbnchips"}} |
Poison Mask
Slip a toxic overlay onto the target's preferred interface so repeated use starts hurting them.
What This Skill Does
Use Poison Mask when the right move is not to poison one tile on the floor but to contaminate a specific interface, workflow surface, or operating persona that the target keeps wearing. Poison Mask attaches the cost to continued contact: every repeated use of the same channel, wrapper, queue, ritual, or decision surface becomes more unpleasant, slower, riskier, or more draining. Unlike Poison Face, which punishes staying in one place, Poison Mask punishes continuing to operate through one poisoned surface. Unlike Time Bomb, it is not waiting to go off later; unlike Killer Eye, it is not there to detect passage; unlike Anti Damage, it is proactive rather than retaliatory.
In this chip pack, Poison Mask is treated as a hybrid battle-chip procedure with a shipping-now delivery profile.
Canonical reference input: Poison Mask.
Hermes shelf: Control and Terrain.
When To Use
- The target keeps interacting through one familiar interface, wrapper, queue, role, or workflow layer that should become costly to keep using.
- You need repeated-contact attrition rather than positional denial on one fixed tile.
- The strongest move is to make an old operating surface unpleasant enough that the target removes it, abandons it, or migrates to a cleaner lane.
Prerequisites
- Name which part of this move is real tool use versus battle-chip framing before you act.
- These procedures rely on the normal tools already present in the active Hermes runtime; this repo does not ship a separate integration layer.
Operator Inputs
- Name the exact interface, queue, approval step, wrapper, role, or recurring workflow surface that should become toxic to keep using.
- Describe what ongoing cost the poison should impose: friction, exposure, delay, audit burden, nuisance, or forced migration.
- State what cleaner lane, replacement interface, or unmasked operating mode Hermes wants the target or team to move toward.
- Say how you will recognize success: reduced reuse of the poisoned surface, migration to the cleaner route, or explicit retirement of the masked layer.
Procedure
- Restate the target, success condition, and no-touch boundaries before you spend the chip.
- Collect the operator inputs below so the chip lands on the right panel.
- Name the exact interface, procedural layer, or persona the target keeps wearing.
- Define what each continued touch, pass, or use should cost and what clean alternative Hermes wants to make relatively more attractive.
- Apply the toxic overlay, then direct operators toward the unmasked route, replacement surface, or cleanse condition.