emtech: Instructions file for Codex

AGENTS.md

emtech AGENTS.md is an instructions file for Codex, OpenCode from elvisdragonmao/emtech. It costs 457 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for the emtech project, focused on commit and pull-request messages. They define how to name the changed area and write concise imperative summaries.

In plain words
What is it for?
It helps write Git commit subjects and pull-request guidance using the project’s area-based naming rules.
Why use it?
They keep the project history and pull requests consistent and make it clearer where each change belongs.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is elvisdragonmao/emtech's own configuration. It tells Codex and OpenCode how to work on emtech itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything emtech configures →

Reuse

Borrowing it

Nothing to install: this file belongs to elvisdragonmao/emtech. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/elvisdragonmao/emtech/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/elvisdragonmao/emtech

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for emtech AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/elvisdragonmao/emtech/agents-md/github.svg)](https://agentmods.dev/instructions/elvisdragonmao/emtech/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/elvisdragonmao/emtech/agents-md"><img src="https://agentmods.dev/badge/instructions/elvisdragonmao/emtech/agents-md/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.

agentmods 80×15 button for emtech AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/elvisdragonmao/emtech/agents-md"><img src="https://agentmods.dev/badge/instructions/elvisdragonmao/emtech/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 457 This file is loaded in full into every session.
When invoked 457 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00457 $0.00457
Opus 5.5 $0.00183 $0.00183
Sonnet 5.5 $0.00091 $0.00091
Haiku 4.5 $0.00046 $0.00046

Measured 2mo ago against content hash 1ae7bb7daa4c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

emtech 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 2mo 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.

AGENTS.md · 39 lines

How it starts

The opening of the file, as written. The whole thing — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repository Guidelines

Commit And PR Guidance

Use Linux kernel/Git-style commit subjects with a concrete area, subsystem, component, directory, package, or file prefix:

area: imperative patch summary
sub/sys: imperative patch summary

The prefix should name the repository area primarily changed. Prefer specific prefixes such as a directory, package, file, subsystem, or component name.

Do not use generic Conventional Commit prefixes such as fix:, feat:, chore:, docs:, or refactor: unless they are actual repository areas in this repository. The prefix should describe where the change belongs, not what type of change it is.

Use an imperative verb in the summary after the colon, such as fix, clarify, split, validate, rename, remove, add, update, document, etc. Do not use past tense verbs like fixed or added.

When a patch spans multiple areas, choose the narrowest common area if one exists. If no clear common area exists, use the primary behavior changed rather than listing multiple unrelated prefixes.

The summary after the colon should briefly describe what the patch does, because it becomes the first line shown in the git changelog. Keep it short, imperative, and specific. Prefer subjects under 72 characters. Use lowercase for the first word after the colon unless it is a proper noun, and do not end the subject with a period.

Examples:

storybook: clarify build ownership
web/routes: split route-level chunks
ui/field: fix select menu positioning
server/auth: validate session cookie
githooks.txt: improve the intro section

Use a commit body when the reason for the change is not obvious from the diff. Explain why the change is needed, not just what changed.

PRs should describe the changed area, summarize the user-visible or developer-visible impact, list validation commands run, link related issues, and include screenshots for visible web UI changes.

If no validation was run, state that explicitly and explain why. Do not claim to have run commands that were not actually executed.

Read the full file on GitHub · 39 lines

Changes

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.

  1. 2mo ago First seen · 39 lines · 457 tokens per session scan A 1ae7bb7daa4c

Subscribe to this mod's changes

emtech AGENTS.md is an instructions file published in the GitHub repository elvisdragonmao/emtech (21 stars, last pushed 12d ago), licensed Apache-2.0. It adds 457 tokens to every session, about $0.0018 per session on Opus 5.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-09-03.

Related

emtech AGENTS.md compared with instructions from other repositories

emtech AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
emtech AGENTS.mdelvisdragonmao/emtechInstructions file2112d agoApache-2.0A457Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode