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/polarity/app.spectrum.analyzer/agents-mdgit clone --depth 1 https://github.com/polarity/app.spectrum.analyzerWrote 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/polarity/app.spectrum.analyzer/agents-md)<a href="https://agentmods.dev/instructions/polarity/app.spectrum.analyzer/agents-md"><img src="https://agentmods.dev/badge/instructions/polarity/app.spectrum.analyzer/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.00858 | $0.00858 |
| Opus 5 | $0.00429 | $0.00429 |
| Sonnet 5 | $0.00172 | $0.00172 |
| Haiku 4.5 | $0.00086 | $0.00086 |
Grade A, and why
app.spectrum.analyzer 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agents Guide
This file gives coding agents a project-specific guide for app.spectrum.analyzer.
Project Scope
- This repository is a browser-based spectrum analyzer built with vanilla HTML, CSS, and JavaScript modules.
- The app captures live audio input, computes FFT data in the browser, and renders a fullscreen frequency spectrum on canvas.
- Keep the project framework-free unless the user explicitly asks for a stack change.
Architecture Map
index.html: Entry document, metadata, root canvas, controls shell, descriptive copy, and footer links.styles.css: Current global layout and control styling.main.js: App bootstrap, UI assembly, start button wiring, and canvas setup.audioSetup.js: Audio device enumeration,AudioContextcreation, analyzer setup, and media stream connection.audioProcessing.js: Threshold, RMS, and slope-weight state plus spectrum-processing helpers.drawingFunctions.js: Main render loop, canvas resize logic, peak detection, labels, and guide rendering.uiComponents.js: Dynamic slider and color-picker creation for the controls panel.utils.js: Shared colors, frequency helpers, note detection, and calibration logic..github/instructions/: Editor and agent guidance already present in the repo; keep new docs aligned with it.docs/overview.md: Human-readable project overview and runtime flow.docs/design-system.md: Current visual direction and target alignment withapp.vectorscope.
Conventions To Follow
- JavaScript style follows StandardJS conventions used in the repo:
- 2-space indentation
- No semicolons
- Keep UI/bootstrap logic in
main.js, audio device and analyzer setup inaudioSetup.js, and drawing logic indrawingFunctions.js. - Preserve the current fullscreen spectrum layout unless the user explicitly asks for a structural UI change.
- When adjusting visuals, prefer centralized theme tokens in CSS over adding more hard-coded colors in JS or inline styles.
- Avoid introducing frameworks, build tooling, or bundlers for simple 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.
- 4d ago First seen · 77 lines · 858 tokens per session scan A b79bf3f4ff07
app.spectrum.analyzer AGENTS.md is an instructions file published in the GitHub repository polarity/app.spectrum.analyzer (21 stars, last pushed 5mo ago), licensed MIT. It adds 858 tokens to every session, about $0.0043 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.