Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/serejaris/kimi-skillsnpx agentmods add skills/serejaris/kimi-skills/murder-mysteryWrote 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/serejaris/kimi-skills/murder-mystery)<a href="https://agentmods.dev/skills/serejaris/kimi-skills/murder-mystery"><img src="https://agentmods.dev/badge/skills/serejaris/kimi-skills/murder-mystery/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/serejaris/kimi-skills/murder-mystery"><img src="https://agentmods.dev/badge/skills/serejaris/kimi-skills/murder-mystery.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.00063 | $0.04106 |
| Opus 5 | $0.00032 | $0.02053 |
| Sonnet 5 | $0.00013 | $0.00821 |
| Haiku 4.5 | $0.00006 | $0.00411 |
Grade A, and why
murder-mystery 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 9d 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Murder Mystery Writing (剧本杀)
Sub-skill of general-writing. Inherits shared principles, anti-AI discipline, and quality gates.
CRITICAL — Spoiler Isolation Rule: Character writers are ISOLATED from each other. Each
character_writerreceives ONLY their character's filtered truth. NEVER pass another character's secrets to a writer.
CRITICAL — Review → Fix Brief → Dispatched Subagent: When a review finds issues, translate them into a detailed fix brief (file paths, quoted findings, expected outcome, scope boundary, self-check) and dispatch a fresh subagent to apply the fix. Never use inline sed/edit_file fixes. Exception:
logic_checkerfailures may require truth-level fixes that the orchestrator coordinates across documents.
CRITICAL — Anti-Read-Loop Rule: The orchestrator must begin truth design (Stage 1) within 10 iterations. If the orchestrator has spent 10+ iterations only reading files without starting truth design, it is in a read-loop. Stop reading, start truth design from what you have immediately.
CRITICAL — Step Budget & Delivery: You have a limited step budget. Plan delivery accordingly:
- Standard murder mysteries (4-8 players): fully achievable in one session. Design truth, write all scripts, review, assemble, convert to .docx.
- Complex scenarios (8+ players, multiple rounds): prioritize truth + character scripts + host guide. Deliver completed components with .docx.
- Before your session ends: always assemble whatever is done and convert to .docx — never end with only raw script files.
Trigger Keywords
剧本杀, murder mystery, 推理本, 情感本, 恐怖本, 机制本, 阵营本, LARP script, 谋杀之谜, 线索设计, 剧本杀主持
File Paths
Output Directory Structure
/mnt/agents/output/
├── research/ # User uploads (venue info, player preferences)
├── {project_name}.truth.md # Master truth document (orchestrator-only)
├── {project_name}.timeline_grid.md
├── {project_name}.spoiler_matrix.md
├── documents/
│ ├── {project_name}.character_web.md
│ └── {project_name}.clue_inventory.md
└── scripts/
├── {project_name}.{character_name}.md
└── {project_name}.host_guide.md
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.
- 9d ago First seen · 277 lines · 63 tokens per session scan A a1b24653714c
murder-mystery is a skill published in the GitHub repository serejaris/kimi-skills (6 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 4,106 once invoked, about $0.0003 per session on Opus 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-09-03.
Other skills, from other repositories
offensive-wifi
Wireless / 802.11 attack methodology for red team engagements and wireless security assessments. Covers monitor-mode setup, WPA/WPA2-PSK handshake capture and PMKID attacks, WPA3 SAE downgrade and Dragonblood, WPA-Enterprise (EAP) attacks (MSCHAPv2 cracking, EAP-TLS cert theft, evil-twin RADIUS), Karma / Known Beacons…
syndic
Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…
offensive-bluetooth-classic
Bluetooth Classic (BR/EDR) attack methodology — device discovery, service enumeration via SDP, LMP/L2CAP layer attacks, legacy PIN cracking (BlueBorne / KNOB), Bluetooth file-transfer abuse (BlueSnarfing legacy), unauthenticated profile abuse (HSP, HFP, OPP), and modern relevance against older industrial / automotive…
design-md-validator
Validate DESIGN.md files against the official Google specification using the @google/design.md CLI linter. Works with local files. Use when the user wants to lint a DESIGN.md, check spec compliance, find broken token references, verify WCAG contrast ratios, diff two versions, export tokens to Tailwind or DTCG format…
agent-wiki
Incremental LLM-friendly wiki generator for Obsidian note vaults. Use when: (1) Building wiki from notes, (2) Ingesting notes to wiki, (3) Obsidian LLM wiki, (4) Incremental knowledge base management. Triggers: 'build wiki from notes', 'ingest notes to wiki', 'Obsidian LLM wiki', 'incremental knowledge base'.
agent-ready-oauth-protected-resource
Sub-skill de agent-ready-cloudflare: Implement OAuth Protected Resource Metadata.