agent-notify AGENTS.md

A set of instructions for coding agents working on the AgentNotify repository, covering startup, Git branches, security safeguards, and required quality checks.

In plain words
What is it for?
Use it when beginning or continuing repository work, creating development branches, making changes, and verifying the result.
Why use it?
It provides a repeatable way to inspect the project, preserve existing work, protect secrets, and record important decisions.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/akash97p/agent-notify/agents-md
Clone the repo
git clone --depth 1 https://github.com/Akash97p/agent-notify

Made for: Codex, OpenCode.

Per session 738 This file is loaded in full into every session.
When invoked 738 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00738 $0.00738
Opus 5 $0.00369 $0.00369
Sonnet 5 $0.00148 $0.00148
Haiku 4.5 $0.00074 $0.00074

Measured 2d ago against content hash bd72f2af10ef, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

agent-notify 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.

AGENTS.md · 65 lines

How it starts

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

AgentNotify agent workflow

These instructions apply to every coding agent working in this repository.

Start or resume work

  1. Read docs/DEVELOPMENT_STATE.md, docs/FEATURE_BACKLOG.md, TODO.md, and the relevant architecture/security documentation.
  2. Inspect git status, the current branch, and recent commits before editing.
  3. Preserve user changes and runtime secrets. Never read or print the bearer token unless direct API debugging was explicitly requested.
  4. Update docs/DEVELOPMENT_STATE.md whenever a decision, verification result, migration, or next step would otherwise be lost after context compaction.

Local Git workflow

  • This repository is local-only unless the user explicitly asks to configure or use a remote.
  • main is the stable release line. Never edit or commit while checked out on main.
  • dev is the integration branch. Do not implement features directly on dev.
  • Create each branch from an up-to-date local dev:
    • feature/<short-name> for product capabilities;
    • fix/<short-name> for defects;
    • docs/<short-name> for documentation;
    • test/<short-name> for test-only work;
    • chore/<short-name> for tooling and maintenance.
  • Keep commits focused and use imperative Conventional Commit subjects such as feat: add webhook delivery.
  • Build and test the branch in proportion to its risk. Update documentation and migrations in the same branch as the behavior they describe.
  • Merge a verified branch into local dev with git merge --no-ff. Delete the local topic branch after the merge when safe.
  • Start the next topic branch from the newly merged dev.
  • Never rewrite shared history, force-push, or use destructive Git commands.

Required quality gates

Run Windows .NET tooling through the repository scripts from WSL:

./scripts/build.sh
./scripts/test.sh
./scripts/package.sh

For narrow iterations, targeted tests are acceptable during development; the full build and test suite are required before merging to dev. Packaging is required when installer payload, embedded resources, publish settings, or release automation changes.

Read the full file on GitHub · 65 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. 2d ago First seen · 65 lines · 738 tokens per session scan A bd72f2af10ef

Subscribe to this mod's changes

agent-notify AGENTS.md is an instructions file published in the GitHub repository Akash97p/agent-notify (1 stars, last pushed 2d ago), licensed MIT. It adds 738 tokens to every session, about $0.0037 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.