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 Totes-MickGOATs/opus-pocus --skill the-room-of-requirementgit clone --depth 1 https://github.com/Totes-MickGOATs/opus-pocusWrote 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/totes-mickgoats/opus-pocus/the-room-of-requirement)<a href="https://agentmods.dev/skills/totes-mickgoats/opus-pocus/the-room-of-requirement"><img src="https://agentmods.dev/badge/skills/totes-mickgoats/opus-pocus/the-room-of-requirement/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/totes-mickgoats/opus-pocus/the-room-of-requirement"><img src="https://agentmods.dev/badge/skills/totes-mickgoats/opus-pocus/the-room-of-requirement.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.00169 | $0.01583 |
| Opus 5 | $0.00084 | $0.00792 |
| Sonnet 5 | $0.00034 | $0.00317 |
| Haiku 4.5 | $0.00017 | $0.00158 |
Grade A, and why
the-room-of-requirement 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 12d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🦋 The Room of Requirement
"Your repo asked for instructions it never had. Here they are."
Every other pass in this book grades instructions that exist. A repo with no memory file gets nothing from them — a full sheet of honest verdicts of no subject, truthful and useless. That repo is the one most likely to benefit from anything at all, and it is the one the book had no answer for.
This is the only pass that writes rather than grades. It still proposes: the file is a fix-table row like any other, and nothing lands until the user approves it.
What to scan
Inputs, in order of authority. Later sources never override earlier ones — they fill gaps.
- The repo's own machinery. Package manifests and lockfiles (which package manager is real,
not which is fashionable), script targets, CI workflow steps, linter and formatter config,
test runner config, the directory layout, and whatever
.gitignoreand generated-file markers say is not hand-written. - README and CONTRIBUTING. Conventions the project already states in prose. Extract, do not restate: if the README says it well and the model reads the README, the memory file needs the rule only when a session would act wrongly without it.
- Correction history, if it exists.
the-remembrall's clusters are the strongest possible input here — a rule the human has already had to give three times, with its wording settled. Skip this input silently when there are no transcripts; do not block on it.
Derive, never invent. Every proposed line cites what it came from — a script name, a workflow step, a config key, a transcript correction. A line you cannot cite is a guess about someone else's project, and it will be obeyed exactly as hard as the true ones.
What goes in
Four things, and the file is mostly done:
- The commands. Build, test, lint, typecheck, run — exact and copy-pasteable, with the right package manager. This is the single highest-value content and the one thing the model cannot infer reliably: it self-verifies its reasoning, not your toolchain.
- The two or three conventions a new contributor gets wrong. Not the style guide — the surprises. Which directory is generated, which file is the source of truth for a value that appears in three places, the import path that looks right and isn't.
- What is generated or vendored. Anything hand-edits get overwritten in, anything a tool owns. Cheap to state, expensive to discover by losing work.
- Anything destructive that must be confirmed first. Migrations, deploys, history rewrites, anything that reaches a shared system.
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.
- 12d ago First seen · 104 lines · 0 tokens per session scan A 267d594f9579
the-room-of-requirement is a skill published in the GitHub repository Totes-MickGOATs/opus-pocus (10 stars, last pushed 1mo ago), licensed MIT. It adds 169 tokens to every session and 1,583 once invoked, about $0.0008 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-08-31.
Other skills, from other repositories
strategic-compact
Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction. Use when a session is approaching a context limit and a task phase is a natural place to compact.
unified-memory
Share durable, inspectable context and handoffs between Claude, Codex, Hermes, Cursor, OpenCode, and other agents through the local ECC Memory Vault. Use when an agent must save work state, transfer context, resume another agent's task, or search shared project knowledge.
agents-md-improver
Audit and improve project-rules files (AGENTS.md, CLAUDE.md, .agents/instructions, local overrides) so the agent keeps accurate project context. Use when the user asks to check, audit, review, update, improve, or fix their AGENTS.md or CLAUDE.md, mentions "project rules maintenance" or "agent context optimization", or…
agents-md-revise
Capture learnings from the current session into the project-rules file (AGENTS.md, CLAUDE.md, or local override) so future sessions benefit. Use when the user says "revise the rules", "update AGENTS.md / CLAUDE.md with what we just learned", "save this to project memory", "remember this for next time", or at the end…
report
Writes the session final report to a file, then prints only the path and a one-line summary. Fires when the prompt contains "Report per memstack:report", and also when the prompt begins with a standing trigger configured through MEMSTACKREPORTONTASKPROMPTS or MEMSTACKREPORTTRIGGERS. Dormant otherwise.
token-optimization
Use when the user says 'token optimization', 'save tokens', 'context window', 'reduce tokens', 'token stack', or 'TokenStack', or asks about extending context window capacity. Covers TokenStack, the built-in compression proxy that shrinks Claude Code tool output before it reaches the Anthropic API. Do NOT use for…