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/cssgit clone --depth 1 https://github.com/polarity/app.spectrum.analyzerWhat 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.00092 | $0.00092 |
| Opus 5 | $0.00046 | $0.00046 |
| Sonnet 5 | $0.00018 | $0.00018 |
| Haiku 4.5 | $0.00009 | $0.00009 |
Grade A, and why
app.spectrum.analyzer css.instructions.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 2d 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
CSS Instructions
- Keep layout and presentation in CSS rather than inline HTML styles or JavaScript-generated style strings.
- When visual cleanup starts, move shared colors, borders, spacing, and radii into semantic custom properties.
- Preserve the spectrogram app's wide canvas-first composition unless the task explicitly changes layout.
- Reuse shared tokens before adding new constants.
- Keep property ordering readable and consistent across rules.
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.
- 2d ago First seen · 11 lines · 92 tokens per session scan A 67d48f204fc9
app.spectrum.analyzer css.instructions.md is an instructions file published in the GitHub repository polarity/app.spectrum.analyzer (21 stars, last pushed 5mo ago), licensed MIT. It adds 92 tokens to every session, about $0.0005 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
diffusers AGENTS.md
AGENTS.md instructions for huggingface/diffusers, a project described as: 🤗 Diffusers: State-of-the-art diffusion models for image, video, and audio generation in PyTorch.
comfy-prompt-studio AGENTS.md
Instructions for yxhpy/comfy-prompt-studio, covering agents.md - ai 代理配置文档, ai 提供商, 1. ollama (默认), 2. gemini and 提示词生成服务.
davinci-resolve-mcp AGENTS.md
Instructions for apvlv/davinci-resolve-mcp, covering project knowledge base, structure, where to look, code map and conventions.
lianhuanhua-skills AGENTS.md
Instructions for littlewindy123/lianhuanhua-skills, covering agents.md, project goal, architecture rules, commands and before committing.
framer-motion-skills copilot-instructions.md
Copilot instructions for C-Jeril/framer-motion-skills, covering framer motion ai skills, available skills, usage, recommendations and code examples.
editor-pro-max CLAUDE.md
Claude Code instructions for Hainrixz/editor-pro-max, covering editor pro max — ai video editor by @soyenriquerocha, auto-setup (important — run on first interaction), quick start, architecture and how to create a new video.