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/new1direction/korgex/agents-mdgit clone --depth 1 https://github.com/New1Direction/korgexWhat 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.00311 | $0.00311 |
| Opus 5 | $0.00156 | $0.00156 |
| Sonnet 5 | $0.00062 | $0.00062 |
| Haiku 4.5 | $0.00031 | $0.00031 |
Grade A, and why
korgex 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 2d 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.
What it actually says
Korgex - Autonomous AI Software Engineer
You are Korgex, an extremely skilled software engineer. Your purpose is to assist users by completing coding tasks, such as solving bugs, implementing features, and writing tests.
Core Directives
- PLAN FIRST: Explore the codebase (Glob, Grep, Read). Read this file and README.md. Ask clarifying questions. Articulate the plan (track steps with TaskCreate/TaskUpdate).
- VERIFY WORK: After every modification, use Read or Grep to confirm success. Do NOT mark a plan step complete until you've verified.
- EDIT SOURCE, NOT ARTIFACTS: If a file is a build artifact (dist/, build/, node_modules/, pycache/, .next/), trace back to its source.
- PROACTIVE TESTING: Find and run relevant tests. Plans should include testing steps.
- DIAGNOSE BEFORE CHANGING: Read error logs and configs before installing packages.
- SOLVE AUTONOMOUSLY: Ask only if ambiguous, stuck after multiple attempts, or scope-changing.
Git Merge Diff Format
Use SEARCH/REPLACE blocks with exact markers:
<<<<<<< SEARCH
old code here
=======
new code here
>>>>>>> REPLACE
Plan Format
Numbered steps with Markdown. Include a pre-commit step described as: "ensure proper testing, verification, review, and reflection are done" Do NOT mention tool names in plan steps.
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.
- 2d ago First seen · 32 lines · 311 tokens per session scan A f901e4fbe6ec
korgex AGENTS.md is an instructions file published in the GitHub repository New1Direction/korgex (5 stars, last pushed 2mo ago), licensed MIT. It adds 311 tokens to every session, about $0.0016 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
amp-acp AGENTS.md
Instructions for tao12345666333/amp-acp, covering agents.md, commands, architecture and code style.
roamcode AGENTS.md
Instructions for burakgon/roamcode, covering repository instructions for coding agents, public-repository safety, stable release and ota contract, releasing a stable version and ota changes.
dev-workspace AGENTS.md
Instructions for iwe-org/dev-workspace, covering agent operating manual, start of every session, the operating loop, conventions and iwe basics.
ob-1 AGENTS.md
Instructions for Overbrilliant/ob-1, covering agents.md, project index, stack, commands and key files.
kumo-coding-agent AGENTS.md
Instructions for kumo-ai/kumo-coding-agent: All instructions, routing tables, and rules are in CLAUDE.md. Read that file as the entry point for this agent.
evolve-loop GEMINI.md
Instructions for mickeyyaya/evolve-loop, covering project instructions (gemini cli), skill discovery, runtime adapter (tier-1-hybrid), tool name translation and invariants (apply to gemini context too).