run-pulse

run-pulse is a skill for Claude Code from thangnguyenworkspace/industry-pulse. It costs 56 tokens per session (9,782 once invoked), scanned C, original, MIT.

A watchlist-based research pipeline that collects updates from LinkedIn, X, RSS feeds, and email, then classifies and combines them into a neutral brief. A watchlist is a set of people, accounts, feeds, or senders being monitored.

In plain words
What is it for?
Use it to monitor selected sources over a chosen time window, limit items per source, tag signals by domain, and produce a consolidated intelligence brief.
Why use it?
It reduces the work of checking several information sources and turns separate updates into one concise account of what happened and why it may matter.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions subagents; positional $N argument.

Good fit Use it to monitor selected sources over a chosen time window, limit items per source, tag signals by domain, and produce a consolidated intelligence brief.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/thangnguyenworkspace/industry-pulse/run-pulse
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.

Any agent
npx skills add thangnguyenworkspace/industry-pulse --skill run-pulse
Clone the repo
git clone --depth 1 https://github.com/thangnguyenworkspace/industry-pulse

Made for: Claude Code.

Wrote 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.

agentmods badge for run-pulse

README.md
[![agentmods](https://agentmods.dev/badge/skills/thangnguyenworkspace/industry-pulse/run-pulse/github.svg)](https://agentmods.dev/skills/thangnguyenworkspace/industry-pulse/run-pulse)
Your own site
<a href="https://agentmods.dev/skills/thangnguyenworkspace/industry-pulse/run-pulse"><img src="https://agentmods.dev/badge/skills/thangnguyenworkspace/industry-pulse/run-pulse/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.

agentmods 80×15 button for run-pulse

Your own site · 80×15
<a href="https://agentmods.dev/skills/thangnguyenworkspace/industry-pulse/run-pulse"><img src="https://agentmods.dev/badge/skills/thangnguyenworkspace/industry-pulse/run-pulse.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 9,782 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00056 $0.09782
Opus 5 $0.00028 $0.04891
Sonnet 5 $0.00011 $0.01956
Haiku 4.5 $0.00006 $0.00978

Measured 12d ago against content hash 364a368f0dc4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade C, and why

run-pulse scanned grade C 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 12d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

Set `rss_raw_dir = output/raw/rss/rss-raw-{report_date}/`. If it already exists, remove it first (`rm -rf {rss_raw_dir}`): it can only be residue from an earlier same-day run, a completed same-day run is caught separatel
.claude/skills/run-pulse/SKILL.md · 374 lines

How it starts

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

Run Pulse

Argument: $ARGUMENTS (optional, all flags optional with defaults; see Runtime Inputs)

Crawl four source-types, classify and domain-tag each in parallel classifier sub-agents, then synthesize one neutral signals brief: the main thread authors a signals-only, third-person brief that states what happened across your watchlist and why it matters. The brief is the reusable core's final artifact and the handoff point, your own relevance layer (and any delivery) attaches downstream at the seam (§3.0 Step 5).


Preamble

Runtime Inputs

Parse $ARGUMENTS for these optional flags; apply defaults when absent:

--days={N}                     [positive integer; default 1; time window passed to every crawl leaf]
--linkedin-max-posts={N}       [positive integer; default 3; per-URL cap for the LinkedIn leaf]
--email-max-per-sender={N}     [positive integer; default 10; per-sender cap for the email leaf]
--x-max-per-handle={N}         [positive integer; default 5; per-handle cap for the X leaf]
--rss-max-items-per-feed={N}   [positive integer; default 15; per-feed cap for the RSS leaf]

All flags optional. Invalid values (non-positive integers, malformed) → halt with the matching §6.0 row.

Global References

All paths are repo-relative (the skill runs with the repo root as the working directory) and are the configuration surface, repoint any of them to your own layout. The config/ inputs are the working copies you create from the shipped .example templates (copy config/profile.example.mdconfig/profile.md, each config/watchlists/{lane}-watchlist.example.mdconfig/watchlists/{lane}-watchlist.md); output/ is gitignored and regenerable per run.

PROFILE_PATH               = config/profile.md
PROFILE_DOMAIN_ENUM        = config/profile.md §3.0   (the domain enum + scope/boundary classifier contract, the tagging vocabulary)
LINKEDIN_WATCHLIST_PATH    = config/watchlists/linkedin-watchlist.md
EMAIL_WATCHLIST_PATH       = config/watchlists/email-watchlist.md
X_WATCHLIST_PATH           = config/watchlists/x-watchlist.md
RSS_WATCHLIST_PATH         = config/watchlists/rss-watchlist.md
RAW_DIR                    = output/raw/      (gitignored; per-source-type subdirs)
TAGGED_DIR                 = output/tagged/   (gitignored; per-run tagged-output files)
REPORTS_DIR                = output/reports/  (the briefs; gitignored by default, repoint or un-ignore to keep them)
TAGGED_SCHEMA              = schemas/schema-pulse-tagged-output.md
REPORT_SCHEMA              = schemas/schema-pulse-report.md
RUN_DIR                    = output/reports/pulse-report-{report_date}/   (per-run folder)
BRIEF_PATH                 = {RUN_DIR}pulse-report-{report_date}.md   (the neutral signals brief, the public artifact and the handoff to your relevance layer)
L1_TOKEN_BUDGET            = 25000   (per-RSS-worker raw-token budget; drives the RSS volume auto-scaler bin count)
L1_CONCURRENCY_CAP         = 14      (max parallel classifier workers; tune to your harness's concurrency limit)
SOURCES_PER_WORKER         = 30      (per-bin source cap for the count-sharded X + LinkedIn lanes; a dial, not a wall, dial down for wide --days windows, a raised per-source post cap, or the heavier LinkedIn lane. Daily defaults assumed: 5 posts/X-handle, 3/LinkedIn-URL, 1-day window.)

Read the full file on GitHub · 374 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. 12d ago First seen · 374 lines · 56 tokens per session scan C 364a368f0dc4

Subscribe to this mod's changes

run-pulse is a skill published in the GitHub repository thangnguyenworkspace/industry-pulse (4 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 9,782 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

competitor-x-ray

Decode any set of competitors into their ICP (ideal customer profile), their funnel (how a stranger becomes a customer), and their monetization (every revenue stream and price point). Researches each competitor against real sources and synthesizes a cross-competitor comparison. Use whenever the user wants to research…

Mahanaicoach/competitor-x-ray · 221 tokens

subagent-driven-development

Execute plans via delegatetask subagents (2-stage review).

NousResearch/hermes-agent · 17 tokens

mcporter

List, auth, and call MCP servers/tools from the terminal.

NousResearch/hermes-agent · 16 tokens

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

article-writing

Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.

affaan-m/ECC · 57 tokens

build-ui-components-and-systems

A guide for building reusable UI components and design systems: shared visual rules, component interfaces, behavior, accessibility requirements, documentation, packaging, and version management. A design system is a maintained set of parts and rules that multiple screens or products can share.

EverMind-AI/Raven · 101 tokens