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/unraid/apprise-go/agents-mdgit clone --depth 1 https://github.com/unraid/apprise-goWhat 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.00306 | $0.00306 |
| Opus 5 | $0.00153 | $0.00153 |
| Sonnet 5 | $0.00061 | $0.00061 |
| Haiku 4.5 | $0.00031 | $0.00031 |
Grade A, and why
apprise-go 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.
What it actually says
AGENTS.md
This repo is the Go port of Apprise. Use this file as a quick runbook when resuming work.
Project layout
- Python reference:
../apprise - Go port: this directory (
apprise-go)
Environment
- Python virtualenv:
apprise-go/.venvwithapprise+cryptographyinstalled (recreate if repo path changes) - Go module:
github.com/unraid/apprise-go - CLI binary name:
apprise(drop-in goal)
Workflow
- Tests should compare Go behavior to the installed Python apprise using a local capture server.
- Request-spec parity is driven by provider folders in
internal/parity/providers/<provider>withmanifest.jsonandcases.json. - Keep Go version strings aligned with upstream apprise (see
internal/version/version.go). - Request-spec parity uses
internal/testutil/scripts/capture_request.py(keeps User-Agent only when Python explicitly sets it). - Request-spec parity now compares full request sequences from Python and Go
Sendcalls. - Golden request fixtures live at
internal/parity/providers/<provider>/golden.json. Regenerate with.venv/bin/python internal/testutil/scripts/update_golden.py. - CI parity setup scripts:
scripts/ci/setup_parity_env.shandscripts/ci/run_parity_tests.sh.
Process log
- See
PROCESS.mdfor current status, setup, and next 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.
- 3d ago First seen · 25 lines · 306 tokens per session scan A a325cbf831d5
apprise-go AGENTS.md is an instructions file published in the GitHub repository unraid/apprise-go (101 stars, last pushed 9d ago), licensed BSD-2-Clause. It adds 306 tokens to every session, about $0.0015 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
no-mistakes AGENTS.md
AGENTS.md instructions for kunchenguid/no-mistakes, covering agents.md and maintaining this file.
trpc-agent-go AGENTS.md
AGENTS.md instructions for trpc-group/trpc-agent-go, covering agents.md, project overview, engineering principles, go design conventions and implementation workflow.
azure-sdk-for-go go-code.instructions.md
Instructions for Azure/azure-sdk-for-go: All code should follow the guidelines from the Azure Go SDK Guidelines. This document is a summary of the most important guidelines to follow when contributing to the Azure Go SDK.
goai AGENTS.md
Instructions for zendev-sh/goai, covering agents.md - goai, commands, architecture, key rules and adding providers.
uzomuzo-oss error-handling.instructions.md
Instructions for future-architect/uzomuzo-oss, covering error handling, go coding conventions: error handling, 1. always add context to errors with %w, 2. use errors.is and errors.as for error inspection and 3. use errors.join to combine multiple errors.
coral CLAUDE.md
Instructions for cdknorow/coral, covering claude.md - coral go, mission, testing, go unit tests and legacy parity tools (historical reference).