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/christosk92/waveemusic/agents-mdgit clone --depth 1 https://github.com/christosk92/WaveeMusicWrote 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/christosk92/waveemusic/agents-md)<a href="https://agentmods.dev/instructions/christosk92/waveemusic/agents-md"><img src="https://agentmods.dev/badge/instructions/christosk92/waveemusic/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.00384 | $0.00384 |
| Opus 5 | $0.00192 | $0.00192 |
| Sonnet 5 | $0.00077 | $0.00077 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
WaveeMusic 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 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.
What it actually says
AGENTS.md — Wavee
Guidance for AI agents working in this repo. The complete rules are in CLAUDE.md (read it first); this file is
the short form for agents that do not load CLAUDE.md automatically.
- What this is: the Wavee Spotify desktop client, built on the FluentGpu engine in the sibling checkout
..\fluent-gpu($(EngineRoot)inDirectory.Build.props). Engine rules, the UI programming model and thefluentgpuskill live there —..\fluent-gpu\CLAUDE.md,..\fluent-gpu\AGENTS.md. - Build & test:
dotnet build Wavee.slnx(Debug and-c Release),dotnet test src/apps/Wavee.Tests/Wavee.Tests.csproj,Invoke-Pester -Path ops/release/tests. No CI exists; releases are local (ops/release/wavee-release.ps1). - Out of scope (never read/edit):
src/apps/.native/**,src/apps/Wavee.PlayPlay/**,private-runtimes/**,src/apps/tmp_*,ops/tools/playplay_*,ops/tools/x64_*,ops/*/pyghidra*,docs/plans/wavee/{wavee-playplay*,playplay-*,spotiload-offline-path}.md,**/playplay-runtime.json— the private PlayPlay workspace, fenced by.githooks/pre-commit. - Rules: component props freeze at mount (data flows through signals/context/keys); no source-text tests; no env-var switches; no legacy paths; plans carry real code; only the orchestrator builds/tests/launches.
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 · 16 lines · 384 tokens per session scan A 8df7253746fe
WaveeMusic AGENTS.md is an instructions file published in the GitHub repository christosk92/WaveeMusic (50 stars, last pushed yesterday), licensed MIT. It adds 384 tokens to every session, about $0.0019 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
maui integration-tests.instructions.md
Guidance for GitHub Copilot when working with .NET MAUI integration tests.
maui public-api.instructions.md
Instructions for dotnet/maui, covering public api surface design, api addition rules, publicapi.unshipped.txt, obsolescence and removal and visibility decisions.
maui performance-hotpaths.instructions.md
Instructions for dotnet/maui, covering performance-critical path rules, hot paths in maui, allocation avoidance, caching and invalidation and collection iteration.
moorestech AGENTS.md
AGENTS.md instructions for moorestech/moorestech, covering コーディングの指針, qa（必須）, 互換性とパフォーマンス, 既知の制約（設計上の割り切り） and regionの活用.
bitfinex-net
Use Bitfinex.Net when generating C#/.NET code that interacts with Bitfinex, including Spot, margin, derivatives symbols, funding, REST endpoints, WebSocket subscriptions, account management, market data, or order placement. Triggers on Bitfinex integration requests in C#, .NET, dotnet, F#, or VB.NET context.
Bitfinex.Net copilot-instructions.md
Copilot instructions for JKorf/Bitfinex.Net, covering copilot instructions for bitfinex.net, use bitfinex.net, not raw http, client setup, result handling and api structure.