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/ewrogers/sleephunter4/agents-mdgit clone --depth 1 https://github.com/ewrogers/SleepHunter4Wrote 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/ewrogers/sleephunter4/agents-md)<a href="https://agentmods.dev/instructions/ewrogers/sleephunter4/agents-md"><img src="https://agentmods.dev/badge/instructions/ewrogers/sleephunter4/agents-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.01522 | $0.01522 |
| Opus 5 | $0.00761 | $0.00761 |
| Sonnet 5 | $0.00304 | $0.00304 |
| Haiku 4.5 | $0.00152 | $0.00152 |
Grade A, and why
SleepHunter4 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 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.
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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SleepHunter Repository Guidance
Scope
These instructions apply to the entire repository. Follow any more specific
AGENTS.md file if one is added below a subdirectory in the future.
SleepHunter is a Windows WPF application for automating and observing the Dark Ages game client. Changes can affect live process memory, input, client patches, and user automation, so favor correctness, compatibility, and bounded reads over speculative behavior.
Mandatory Writing Rules
- Never use the Unicode em dash character.
- Never use emojis or pictographic symbols.
- Apply these rules to source code, comments, tests, documentation, changelogs, commit messages, pull request text, issue text, and user-facing copy.
- Use commas, colons, parentheses, or a standard hyphen when punctuation is needed instead of an em dash.
- Do not rewrite unrelated existing text solely to remove older violations. Any text that is added or materially edited must follow these rules.
Repository Layout
src/SleepHunter.App/contains the main .NET 10 WPF application.src/SleepHunter.Updater/contains the Windows updater.tests/SleepHunter.App.Tests/contains the WPF application NUnit tests.data/contains runtime XML data, including the client layout, themes, skills, spells, and staves.docs/contains the mdBook documentation source.CHANGELOG.mdis the authoritative changelog. Documentation deployment copies it into the generated documentation output..github/workflows/defines build, test, documentation, and release behavior.
Working Practices
- Inspect the relevant code, tests, configuration, and current Git status before editing.
- Preserve unrelated user changes and avoid broad cleanup outside the requested scope.
- Make the smallest coherent change that solves the problem.
- Preserve compatibility paths unless the task explicitly removes support for them.
- Add or update tests for behavior that can be validated without a live client.
- Update
CHANGELOG.mdfor user-visible changes. - Report checks that were run and any live-client behavior that still needs manual verification.
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 · 167 lines · 1,522 tokens per session scan A a01608a84935
SleepHunter4 AGENTS.md is an instructions file published in the GitHub repository ewrogers/SleepHunter4 (21 stars, last pushed 5d ago), licensed MIT. It adds 1,522 tokens to every session, about $0.0076 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-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.