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/bobby-cell-commits/open-brain-server/pulsenpx skills add Bobby-cell-commits/open-brain-server --skill pulsegit clone --depth 1 https://github.com/Bobby-cell-commits/open-brain-serverWrote 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/bobby-cell-commits/open-brain-server/pulse)<a href="https://agentmods.dev/skills/bobby-cell-commits/open-brain-server/pulse"><img src="https://agentmods.dev/badge/skills/bobby-cell-commits/open-brain-server/pulse.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.00162 | $0.05286 |
| Opus 5 | $0.00081 | $0.02643 |
| Sonnet 5 | $0.00032 | $0.01057 |
| Haiku 4.5 | $0.00016 | $0.00529 |
Grade A, and why
pulse 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 5d 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 — 526 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pulse — Pipeline & Data Health Report
Produce a comprehensive health and metrics report for Open Brain's pipeline infrastructure and data quality. Rubric-scored assessments, cross-metric pattern detection, cross-run memory, and concrete suggested actions.
Arguments
Parse from user message:
- days: Integer, default 7. The reporting period in days. Usage:
/pulseor/pulse 14.
Set N = days value for all tool calls below.
Set TODAY = current date in YYYY-MM-DD format.
Phase 1: Data Gathering
Call all 9 MCP tools in parallel. There are no dependencies between them.
Parallel calls:
-
pipeline(type="health")— source status + active alerts -
pipeline(type="runs", days=N)— run history for the period -
thought_stats(days=N)— current period type/theme/source/topic breakdown -
thought_stats(days=N*2)— double-window stats (subtract current period to derive prior period) -
analyze(type="density")— graph connectivity at 4 thresholds (0.70, 0.75, 0.80, 0.85) -
analyze(type="hubs", min_connections=5)— cluster nuclei -
dedup_review(limit=30)— duplicate candidates + zone histogram -
pipeline(type="merges", days=N)— recent merge operations -
analyze(type="sources")— per-source counts + cross-source similarity pairs -
Read
TRACKER.md— extract the shipped milestones table (date + what was built) and Feature Status sections (feature name + status). Focus on items shipped within the last 14 days. This context feeds into Section 6.5. -
Glob
research/pulse/*.md, sort filenames descending, skip any file matching TODAY's date, take the first match. Read its YAML frontmatter and extract thefindingsarray. If no prior report exists or the prior report has nofindingsarray, setprior_findingsto an empty list. -
Read
research/pulse/BASELINE.md(if it exists). Parse YAML to extractsuppressandforcelists. If the file does not exist, set both lists to empty.
Items 11-12 have no dependencies on MCP tool calls — run them in parallel with everything else.
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.
- 5d ago First seen · 526 lines · 162 tokens per session scan A 592b1dfcbd8f
pulse is a skill published in the GitHub repository Bobby-cell-commits/open-brain-server (8 stars, last pushed 4mo ago), licensed MIT. It adds 162 tokens to every session and 5,286 once invoked, about $0.0008 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…