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/devswha/oh-my-gajae-code/agents-mdgit clone --depth 1 https://github.com/devswha/oh-my-gajae-codeWhat 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.09064 | $0.09064 |
| Opus 5 | $0.04532 | $0.04532 |
| Sonnet 5 | $0.01813 | $0.01813 |
| Haiku 4.5 | $0.00906 | $0.00906 |
Grade C, and why
oh-my-gajae-code AGENTS.md scanned grade C with 2 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 3d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- **Auto-update is opt-in (`bin/omg-autoupdate.sh`).** The one-shot installer NEVER schedules updates. A user opts in explicitly with `omg-autoupdate.sh enable` (systemd `--user` timer, cron fallback; `--interval`, `--lo Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- **Hardened local engine** (`bin/pack_and_ask.py`, Playwright-based, cross-platform): it is no longer byte-for-byte upstream and carries audited local DOM/security patches. The gjc port also rewrote the shell: skill/com How it starts
The opening of the file, as written. The whole thing — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — working in oh-my-gajae-code
Agent-facing guide for oh-my-gajae-code, a plugin marketplace for Gajae Code (gjc).
Read this before adding or editing plugins. Human-facing intro lives in README.md.
v0.28.0 identity cutover and migration
oh-my-gajae-code is the canonical repository, marketplace/plugin identity, and ./plugins/oh-my-gajae-code source. /omg:* commands remain unchanged.
v0.27.0 was the final old-identity bridge. The canonical installer is https://raw.githubusercontent.com/devswha/oh-my-gajae-code/main/install.sh; old raw.githubusercontent.com/devswha/oh-my-gjc/... URLs do not redirect. Old GitHub repository pages and Git remotes redirect, but active instructions and local checkout names use oh-my-gajae-code.
New installs write only oh-my-gajae-code bindings. The former oh-my-gjc suite-root binding is a read-only fallback for at least 30 days or two releases; it is never rewritten or cleaned up by this cutover. Existing old XDG research data, credentials, and models.yml remain in place.
What this repo is
A single git repo that catalogs installable gjc plugins. One marketplace.json
lists every plugin; each plugin is one directory under plugins/. The format is
compatible with the Claude Code / Codex plugin spec.
Plugins install from the shell CLI — gjc plugin install <name>@<marketplace> …
(TARGETS is plural: install several in one command; --scope user is the default,
--scope project pins to a repo; gjc plugin marketplace add <ref> registers a
catalog; gjc plugin list shows installed). Plugin management is shell-CLI only — gjc has NO /plugin slash command (verified against the core slash registry + live new-user repro 2026-07-08: gjc plugin marketplace add/install/list all rc=0). A /plugin … line typed inside a gjc session is just a chat message, not a command, so all install/uninstall/marketplace steps must run in a terminal. The registry lives at ~/.gjc/plugins/installed_plugins.json. (/plugin slash is Claude-Code syntax — do NOT put it in gjc install docs.)
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.
- 3d ago First seen · 263 lines · 9,064 tokens per session scan C 41e4f9c638b5
oh-my-gajae-code AGENTS.md is an instructions file published in the GitHub repository devswha/oh-my-gajae-code (34 stars, last pushed 14d ago), licensed MIT. It adds 9,064 tokens to every session, about $0.0453 per session on Opus 5. A static security scan graded it C with 2 findings (asks for root, reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.