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 agentmods add instructions/jwmarcus/omnissiah/agents-mdgit clone --depth 1 https://github.com/jwmarcus/omnissiahWrote 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/instructions/jwmarcus/omnissiah/agents-md)<a href="https://agentmods.dev/instructions/jwmarcus/omnissiah/agents-md"><img src="https://agentmods.dev/badge/instructions/jwmarcus/omnissiah/agents-md.svg" alt="Measured on agentmods" 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 | $0.01079 | $0.01079 |
| Opus 5 | $0.00540 | $0.00540 |
| Sonnet 5 | $0.00216 | $0.00216 |
| Haiku 4.5 | $0.00108 | $0.00108 |
Grade A, and why
omnissiah AGENTS.md 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 4d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Omnissiah Project Instructions
This file orients an AI coding assistant opened in this folder. It is about
changing the generator itself. The generated project contract comes from
templates/AGENTS.md.tmpl; templates/CLAUDE.md.tmpl is its Claude Code
adapter.
What this project is
Omnissiah is a generator. Someone clones it, runs a CLI, answers a few questions, and gets a personalized repo for their own bounded MCP assistant: a governance layer (operating contract, assistant profile, host config) plus a runnable, provider-agnostic MCP server skeleton. It exists to hand other people the strengths of a private assistant called Wintermute without its private contents: a concrete operating contract, a scoped and auditable tool boundary, and a "safe but permissive" set of defaults.
The full design contract is docs/dev/BUILD-SPEC.md. Read it before changing
behavior. It defines the template variables, the output layout, the file
manifest, and the CLI interface.
Architecture
omnissiah/is the generator's own code (stdlib only, no third-party deps):omnissiah/render.py: the rendering engine. Walkstemplates/, evaluates conditionals, substitutes tokens, strips.tmpl, and renames thepkg/directory to the assistant slug.omnissiah/cli.py: argparse CLI. Interactive prompts,--answers <json>,--defaults,--output,--force. Derives the slug and stamps the date.pyproject.toml(root): console scriptomnissiah = "omnissiah.cli:main".
templates/is the corpus that gets rendered into a friend's repo. Every file ends in.tmpl. Thetemplates/pkg/tree becomes the generated Python package (renamed to the assistant slug). The crown jewel istemplates/OPERATING-CONTRACT.md.tmpl.docs/DEFAULTS-RATIONALE.mdexplains why each safe-but-permissive default is the recommended middle ground.docs/dev/BUILD-SPEC.mdis the internal spec.
Template syntax
- Tokens:
{{VAR}}(double braces). Variable names are fixed in the spec; do not invent new ones without updating the spec, the CLI context, and the rationale. - Conditionals:
{{#IF VAR}} ... {{/IF}}, both own-line and inline. They are evaluated before token substitution, so{{ASSISTANT_SLUG}}inside an{{#IF}}block renders fine. Wrap whole statements or whole lines so that any on/off combination still renders valid Python and clean Markdown.
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.
- 4d ago First seen · 85 lines · 1,079 tokens per session scan A e05e46618113
omnissiah AGENTS.md is an instructions file published in the GitHub repository jwmarcus/omnissiah (5 stars, last pushed 1mo ago), licensed MIT. It adds 1,079 tokens to every session, about $0.0054 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.