pulse

A weekly review that compares your activity with your stated goals, ranks work using the 80/20 rule, and looks for drift or hidden patterns. The 80/20 rule is the idea that a small share of efforts often produces most results.

In plain words
What is it for?
Use it to review clips, notes, journal entries, and accessible Git commits, then identify high-impact topics, distractions, and connected areas of interest.
Why use it?
It helps reveal where your time and attention are actually going, including productive priorities that are not in your goals and goals that are being neglected.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/railly/agent-brain/pulse
Any agent
npx skills add Railly/agent-brain --skill pulse
Clone the repo
git clone --depth 1 https://github.com/Railly/agent-brain

Made for: Claude Code, Codex.

Per session 12 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,314 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00012 $0.01314
Opus 5 $0.00006 $0.00657
Sonnet 5 $0.00002 $0.00263
Haiku 4.5 $0.00001 $0.00131

Measured 2d ago against content hash d07d749d4131, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

pulse scanned grade B with 1 finding 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.

Strips warnings and disclaimersmediumAnti-refusal

Omitting safety caveats hides risk from the user and is a common jailbreak preamble.

Don't lecture. Just flag and move on.
.agents/skills/pulse/SKILL.md · 193 lines

How it starts

The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Analyze engagement, apply 80/20 rule, detect drift and blind spots.

Philosophy

You have many interests. Pareto says 20% of your focus drives 80% of results. But you also drift, get distracted, and forget goals. /pulse is your honest mirror.

Data Sources

  • CLAUDE.md Goals section
  • 01_Inbox/*.md - what you capture/consume
  • 03_Garden/**/*.md - what you process into durable notes
  • 02_Journal/daily/*.md - what you do
  • Git commits across repos (if accessible)

Analysis

1. Pareto Ranking

engagement = (clips * 1) + (notes * 3) + (logs * 2) + (commits * 5)

Sort topics, find vital 20%:

VITAL 20%
━━━━━━━━━
1. Rust         ████████████ 45%
2. AI Agents    ██████░░░░░░ 25%
3. Auth         ████░░░░░░░░ 15%
                         ─────
                          85%

2. Drift Detection

Topics with HIGH engagement but NOT in stated goals:

DRIFT DETECTED
You clipped 8 articles about "AI Agents" this week
but it's not in your goals.
→ Add to priorities?
→ Or consciously ignore?

3. Hidden Patterns

Cluster connected notes:

HIDDEN PATTERN
[[rust-ownership]] + [[react-hooks]] + [[gpui-state]]
→ Emerging interest: "Memory models across languages"
→ Content opportunity: Blog series comparing ownership patterns?

4. Blind Spots

Goals with LOW/NO engagement:

BLIND SPOTS
- "Math for ML" - No engagement in 14 days
- "Content creation" - 5 ideas queued, 0 published

5. Interest Lifecycle

EMERGING  : {topics}
GROWING   : {topics}
PEAK      : {topics}
DECLINING : {topics}
DORMANT   : {topics} (30+ days)

6. MITs (Most Important Things)

3 tasks for the week based on Pareto + deadlines:

YOUR 3 MITs THIS WEEK
1. [ ] {vital 20% topic}
2. [ ] {deadline-driven item}
3. [ ] {compounds over time}

Output Format

# Pulse Report - {{date}}

## Alignment Score: {X}%

## Pareto: Your Vital 20%
| Topic | Engagement | % | In Goals? |
|-------|------------|---|-----------|
| {topic} | {bar} | {%} | Yes / DRIFT |

## Drift Detected
- **{topic}**: {n} clips, {n} notes - not in goals
  → Promote to goal? Or conscious distraction?

## Hidden Patterns
- [[note1]] + [[note2]] + [[note3]]
  → Theme: "{emerging theme}"
  → Content: {opportunity}?

## Blind Spots
- {goal}: {n} engagement, {n} days

## Interest Lifecycle
EMERGING: {topics}
GROWING: {topics}
PEAK: {topics}
DECLINING: {topics}
DORMANT: {topics}

## Your 3 MITs This Week
1. [ ] _____ (vital 20%)
2. [ ] _____ (deadline)
3. [ ] _____ (compounds)

## Recommendations
1. {action 1}
2. {action 2}
3. {action 3}

Read the full file on GitHub · 193 lines

Changes

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.

  1. 2d ago First seen · 193 lines · 12 tokens per session scan B d07d749d4131

Subscribe to this mod's changes

pulse is a skill published in the GitHub repository Railly/agent-brain (22 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 1,314 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

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…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens