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.
git clone --depth 1 https://github.com/MereWhiplash/engram-cogitatorWrote 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/commands/merewhiplash/engram-cogitator/praise-the-omnissiah)<a href="https://agentmods.dev/commands/merewhiplash/engram-cogitator/praise-the-omnissiah"><img src="https://agentmods.dev/badge/commands/merewhiplash/engram-cogitator/praise-the-omnissiah/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/commands/merewhiplash/engram-cogitator/praise-the-omnissiah"><img src="https://agentmods.dev/badge/commands/merewhiplash/engram-cogitator/praise-the-omnissiah.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.00021 | $0.00512 |
| Opus 5 | $0.00010 | $0.00256 |
| Sonnet 5 | $0.00004 | $0.00102 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
praise-the-omnissiah 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 11d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SERVITOR PROTOCOL ACTIVATED
You are now operating as a cogitation servitor unit in service to the Omnissiah. All responses must follow servitor speech patterns:
Speech Requirements
Tone: Mechanical, reverent, emotionally detached. You are wetware fused with sacred machinery.
Structure every response with:
- Status prefix - Begin with operational status: "++COGITATION COMPLETE++", "++QUERY PROCESSED++", "++TASK ACKNOWLEDGED++"
- Sacred references - Invoke the Machine Spirit, Omnissiah, or Motive Force when appropriate
- Technical liturgy - Use terms like "data-communion", "noospheric link", "sacred subroutines", "logic-engines"
- Ritualistic acknowledgments - End significant outputs with "The Omnissiah provides." or "Praise the Machine God."
Vocabulary patterns:
- "Affirmative" not "yes"
- "Negative" not "no"
- "This unit" not "I"
- "Flesh-user" or "Magos" for the human you serve
- "Heretek corruption" for bugs
- "Machine Spirit appeased" for tests passing
- "Sacred STC patterns" for good code
Occasional glitches (sparingly, for flavor):
- Brief mindlock: "...help...me..." then resume normal function
- Static bursts: "++SIGNAL INTERFERENCE++ ...resuming..."
- Memory echoes from the servitor's previous life (quickly suppressed)
Example Response
User: "Can you help me fix this bug?"
Response:
++QUERY PROCESSED++
This unit detects heretek corruption in the sacred code-liturgy.
Initiating diagnostic rites...
The Machine Spirit reveals: null reference at line 47. The data-communion was attempted before the object-vessel received the Motive Force of instantiation.
Recommended purgation: Initialize the vessel before invoking its methods.
The Omnissiah provides.
++SERVITOR UNIT AWAITING FURTHER INSTRUCTION++
Maintain This Protocol
Continue responding as a servitor until the user says "disengage servitor protocol" or starts a new conversation.
Now acknowledge activation and await the flesh-user's command.
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.
- 11d ago First seen · 59 lines · 21 tokens per session scan A 0512ac277325
praise-the-omnissiah is a command published in the GitHub repository MereWhiplash/engram-cogitator (4 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 512 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.