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/juanchoabdon/ohmyself/agents-mdgit clone --depth 1 https://github.com/juanchoabdon/ohmyselfWrote 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/juanchoabdon/ohmyself/agents-md)<a href="https://agentmods.dev/instructions/juanchoabdon/ohmyself/agents-md"><img src="https://agentmods.dev/badge/instructions/juanchoabdon/ohmyself/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.00504 | $0.00504 |
| Opus 5 | $0.00252 | $0.00252 |
| Sonnet 5 | $0.00101 | $0.00101 |
| Haiku 4.5 | $0.00050 | $0.00050 |
Grade A, and why
ohmyself 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 yesterday.
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.
What it actually says
Agent notes for the ohmyself repo
Deploying (read this before shipping server/MCP changes)
www.ohmyself.ai is the single public origin for all clients (Cursor,
ChatGPT, Claude, OAuth). It is a proxy — the real backend is Railway.
- Deploy server changes to Railway:
cd server && railway up --service ohmyself-api --no-gitignore(Railway does not auto-deploy from GitHub today). --no-gitignoreis required. Root.gitignorehas/versions/andserver/versions/for runtime version data; Railway's default upload respects.gitignoreand can excludeserver/src/core/versions/(the TypeScript source). Without the flag,tscfails withCannot find module './versions/types.js'.- Don't delete
server/.railwayignore. The flag above is all-or-nothing, so it would also uploadnode_modules, which sincesharpcarries platform-specific native binaries. Shipping macOS ARM builds to Railway's linux/amd64 container breaksget_mediaat first use, long after a green deploy. That file excludesnode_moduleswhile keepingsrc/core/versions/. - One backend only: Railway. The old Vercel server copy
(
ohmyself-api.vercel.app) was decommissioned 2026-07-11 — don't recreate it and neververcel deploy --prodfromserver/. Everything goeswww→ Railway. - When changing the MCP tool contract, bump
CONTRACT_VERSIONinserver/src/mcp/tools.ts, then verify live viaget_structureagainsthttps://www.ohmyself.ai/mcp. - After deploy, clients cache the tool list — reconnect (ChatGPT/Claude) or reload (Cursor) to pick up new tools.
- Hosted billing: set
STRIPE_*on Railway andOMS_ENFORCE_PRO=trueonly when you want paywalls live. The webhook path isPOST /webhooks/stripe(proxied from www). Leave enforcement unset for self-host.
Full topology, runbook, and history: docs/DEPLOYMENT.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.
- yesterday Changed · +3 lines · +58 tokens per session 2b3bcbaa1c9a
- 4d ago First seen · 29 lines · 446 tokens per session scan A 14119fb34c85
ohmyself AGENTS.md is an instructions file published in the GitHub repository juanchoabdon/ohmyself (0 stars, last pushed yesterday), licensed MIT. It adds 504 tokens to every session, about $0.0025 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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.
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).