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/akash97p/agent-notify/claude-mdgit clone --depth 1 https://github.com/Akash97p/agent-notifyWrote 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/akash97p/agent-notify/claude-md)<a href="https://agentmods.dev/instructions/akash97p/agent-notify/claude-md"><img src="https://agentmods.dev/badge/instructions/akash97p/agent-notify/claude-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.01598 | $0.01598 |
| Opus 5 | $0.00799 | $0.00799 |
| Sonnet 5 | $0.00320 | $0.00320 |
| Haiku 4.5 | $0.00160 | $0.00160 |
Grade A, and why
agent-notify CLAUDE.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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgentNotify - Claude Code instructions
These instructions apply to all work in this repository.
Start or resume work
- Read
docs/DEVELOPMENT_STATE.md,docs/FEATURE_BACKLOG.md,TODO.md, and the relevant architecture/security documentation. - Inspect
git status, the current branch, and recent commits before editing. - Preserve user changes and runtime secrets. Never read or print the bearer token unless direct API debugging was explicitly requested.
- Update
docs/DEVELOPMENT_STATE.mdwhenever 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.
mainis the stable release line. Never edit or commit while checked out onmain.devis the integration branch. Do not implement features directly ondev.- 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
devwithgit 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
Always go through these scripts. Never invoke dotnet.exe off the Windows PATH.
The scripts resolve the SDK through AGENTNOTIFY_DOTNET_EXE, which defaults to
/mnt/d/dev/dotnet/dotnet.exe. That is the only .NET 10 SDK on this machine:
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.
- 4d ago First seen · 198 lines · 1,598 tokens per session scan A d9abc878d5e7
agent-notify CLAUDE.md is an instructions file published in the GitHub repository Akash97p/agent-notify (1 stars, last pushed today), licensed MIT. It adds 1,598 tokens to every session, about $0.0080 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
coograph brutal-honesty.instructions.md
Global communication style — applies to all workspaces and conversations.
claude-bridge AGENTS.md
Instructions for kadaba/claude-bridge, covering agents.md — using claude-bridge from any ai coding cli, two independent channels, 1. coordination (the conversation), 2. file transfer (the bytes) — same for every tool and workflows.
tidyfactor-design AGENTS.md
Instructions for alwkala/tidyfactor-design, covering ⚡ skill & 24 modular slash commands (7 lifecycle stages) and critical architecture (non-negotiable).
claude-code-second-brain AGENTS.md
Instructions for shofer-dev/claude-code-second-brain, covering agents.md, read first, invariants and working here.
AmbyKit CLAUDE.md
Instructions for ambystechcom/AmbyKit, covering claude code — notes for the ambykit repo and claude-specific.
loadout CLAUDE.md
Instructions for AmElmo/loadout, covering loadout, project structure, tech stack, key commands and test fixtures.