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/2389-research/pulse/claude-mdgit clone --depth 1 https://github.com/2389-research/pulseWrote 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/2389-research/pulse/claude-md)<a href="https://agentmods.dev/instructions/2389-research/pulse/claude-md"><img src="https://agentmods.dev/badge/instructions/2389-research/pulse/claude-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.00728 | $0.00728 |
| Opus 5 | $0.00364 | $0.00364 |
| Sonnet 5 | $0.00146 | $0.00146 |
| Haiku 4.5 | $0.00073 | $0.00073 |
Grade A, and why
pulse 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 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pulse - Journal + Social Media MCP Server
A single Go binary that unifies private journaling and social media into one local-first MCP service.
Names
- Project Codename: BRAINWAVE NITRO
- AI Assistant: Turbo Gecko
- Human Lead: Harp Daddy Supreme
Architecture
Local-first file storage with optional remote API operations for journal and social. Journal entries and social posts are Markdown, config and social identity are YAML, and optional embedding sidecars are JSON.
CLI and MCP journal search use newest-first local substring matching. The embeddings package accepts an Embedder supplied by a caller, but has no production implementation and is not connected to CLI or MCP search.
Repo: https://github.com/2389-research/pulse
Two storage roots:
- Journal: dual-root (project-local
.private-journal/+ user-global~/.private-journal/) - Social:
$XDG_DATA_HOME/pulse/social/or~/.local/share/pulse/social/
MCP Tools (7 total):
process_thoughts- Write journal entry with sectionssearch_journal- Local substring searchread_journal_entry- Read specific entry by pathlist_recent_entries- List entries by datelogin- Set social media identitycreate_post- Create social post (local + optional remote)read_posts- Read social feed with filtering
Remote behavior:
- MCP
process_thoughtswrites locally first, then attempts a best-effort remote write. - With remote config, MCP and CLI social writes attempt the remote service once. Success writes no local post; failure saves locally and returns a warning.
- MCP journal reads/searches use local data only.
- CLI
journal writewrites locally only. - CLI
journal searchandjournal listmerge local and remote entries and fall back to local results on remote errors. - With remote config, MCP
read_postsand CLIsocial feedread remote posts only and return remote errors.
Development
# Run
go run ./cmd/pulse
# Build
go build -o bin/pulse ./cmd/pulse
# Test
go test ./...
# MCP server
./pulse mcp
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 · 84 lines · 728 tokens per session scan A 4afb2db21d96
pulse CLAUDE.md is an instructions file published in the GitHub repository 2389-research/pulse (5 stars, last pushed 23d ago), licensed MIT. It adds 728 tokens to every session, about $0.0036 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 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.
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.