Borrowing it
Nothing to install: this file belongs to niclasvestlund-YT/vibepulse. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/niclasvestlund-YT/vibepulse/main/CLAUDE.mdgit clone --depth 1 https://github.com/niclasvestlund-YT/vibepulseWrote 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/niclasvestlund-yt/vibepulse/claude-md)<a href="https://agentmods.dev/instructions/niclasvestlund-yt/vibepulse/claude-md"><img src="https://agentmods.dev/badge/instructions/niclasvestlund-yt/vibepulse/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/niclasvestlund-yt/vibepulse/claude-md"><img src="https://agentmods.dev/badge/instructions/niclasvestlund-yt/vibepulse/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.01710 | $0.01710 |
| Opus 5.5 | $0.00684 | $0.00684 |
| Sonnet 5.5 | $0.00342 | $0.00342 |
| Haiku 4.5 | $0.00171 | $0.00171 |
Grade A, and why
vibepulse CLAUDE.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 29d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read README.md for the repository structure and build workflow.
Follow CONTRIBUTING.md and docs/maintaining-contributions.md for contributions
and merging. Maintainer changes also go through a PR with passing required
checks. Documented local test omissions do not waive GitHub's merge requirements.
Setting this repo up for someone (secrets, build, flash, tokenserver)? Follow
docs/agent-setup.md — step-by-step, with verifications and a symptom→fix
table. Never flash the board without the user explicitly asking you to.
Over-the-air updates
This workflow applies to the original 2.16 board. Update 2.41 V2, 1.91 Touch and 1.75 over USB using their board-specific guides; OTA and board identification in the update chain are not validated for these ports.
Day-to-day firmware goes over the air: idf.py build && tools/ota-flash.sh
(device IP from git-ignored .ota-device). The full loop, consent model and
troubleshooting live in docs/ota.md — read it before touching anything
OTA. Non-negotiables: the maintenance window opens ONLY from the device (a
3 s KEY3 hold opens SETTINGS, where UPDATE opens it — greyed out without an
address, since a window with no address cannot receive an upload; WIFI opens
the setup window, see docs/wifi.md — or the UPDATE pill on the takeover) —
never claim or imply a
script can; the sender gates (newest-binary-at-send, version printed,
-dirty refused) exist because a stale archived build once froze the panel —
never bypass them with TG_OTA_ALLOW_DIRTY without the user saying so; and
after editing tools/tokenserver/, restart the host service
(macOS: launchctl kickstart -k gui/$(id -u)/se.torget.tokenserver;
Windows has no launchd — the service runs under Task Scheduler, so restart it
with Stop-ScheduledTask, a wait until it has actually stopped, and only then
Start-ScheduledTask on the task VibePulse tokenserver; the task is
registered -MultipleInstances IgnoreNew, so an immediate start is silently
discarded and the service stays down until the five-minute watchdog — the
snippet is under "Restarting the scheduled task" in docs/windows-setup.md.
Never restart it by rerunning install-windows-task.ps1, which
rebuilds the task's command line from that invocation's arguments and so
silently drops the -PublishUrl, -GithubRepo and plan/cost settings it was
installed with) — the running process keeps old code and the panel honestly
shows the gap.
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.
- 29d ago Changed · +3 lines · +60 tokens per session 018f124e15f7
- 1mo ago Changed · +19 lines · +282 tokens per session a2933790eae9
- 1mo ago Changed · +4 lines · +61 tokens per session 1d3dbcdc0475
- 1mo ago Changed · +9 lines · +140 tokens per session 5ff8039c0a49
- 1mo ago Changed · +4 lines · +52 tokens per session b5bc51c46358
- 1mo ago Changed · +10 lines · +163 tokens per session a864f847efac
- 1mo ago Changed · +1 lines · +15 tokens per session e86100a362d5
- 1mo ago First seen · 73 lines · 937 tokens per session scan A b393232856cc
vibepulse CLAUDE.md is an instructions file published in the GitHub repository niclasvestlund-YT/vibepulse (212 stars, last pushed today), licensed MIT. It adds 1,710 tokens to every session, about $0.0068 per session on Opus 5.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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.