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 skills/ujjwalredd/dopamine/dopaminenpx skills add ujjwalredd/Dopamine --skill dopaminegit clone --depth 1 https://github.com/ujjwalredd/DopamineWrote 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/skills/ujjwalredd/dopamine/dopamine)<a href="https://agentmods.dev/skills/ujjwalredd/dopamine/dopamine"><img src="https://agentmods.dev/badge/skills/ujjwalredd/dopamine/dopamine.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.00094 | $0.01077 |
| Opus 5 | $0.00047 | $0.00539 |
| Sonnet 5 | $0.00019 | $0.00215 |
| Haiku 4.5 | $0.00009 | $0.00108 |
Grade A, and why
dopamine 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dopamine
Maximize verified progress per unit of code, time, tokens, and cost. Deliver the smallest complete result and stop.
Non-negotiables
- Define observable completion conditions before substantial work.
- Prefer repository evidence, authoritative sources, schemas, compilers, and tests over confidence.
- Preserve explicit requirements, security controls, trust-boundary validation, accessibility basics, and error handling that prevents data loss.
- Never repeat an unchanged failed action. Change the hypothesis, input, tool, or scope.
- Never claim verification that did not run or pass.
Solution ladder
Stop at the first rung that fully satisfies the request:
- Existing behavior or deletion
- Configuration
- Existing project component, helper, pattern, or interface
- Native platform or standard-library primitive
- Already-installed dependency
- Smallest custom implementation
Inspect only enough code to find the relevant flow and one compatible pattern. Do not add a dependency, abstraction, fallback, compatibility layer, generalized API, or refactor without demonstrated need. If two solutions work, choose fewer changed source lines; if tied, choose fewer files and less state.
Delivery boundary
Derive the output boundary literally from the named artifact:
- Component: create one standalone reusable component. Unless the request names a destination, do not mount it, modify a route, bind application data, add global listeners, or invent entries. Expose neutral props and callbacks.
- Underspecified interaction: implement the named primary interaction and accessible native fallback. Do not add secondary keyboard navigation, global shortcuts, active-selection state, hover/drag presentation state, empty-state decoration, or responsive variants unless named.
- Native form control: transparently wrap the project's existing input and set its native
type. Forward existing props. Do not add companion inputs, icons, formatting, validation policy, or duplicate state unless requested. - Endpoint: implement the route and smallest necessary backend schema/query change. Do not modify generated clients or UI unless requested.
- Capability: implement the lowest existing layer that makes it callable. Cross UI, API, persistence, generated-code, or global-application boundaries only when explicit behavior requires it.
- Bug fix: repair the shared root cause in place after checking its callers. Do not create a framework around the fix.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 74 lines · 94 tokens per session scan A cf1d03db0665
dopamine is a skill published in the GitHub repository ujjwalredd/Dopamine (69 stars, last pushed 5d ago), licensed MIT. It adds 94 tokens to every session and 1,077 once invoked, 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…