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/duthaho/skillhub/pulsenpx skills add duthaho/skillhub --skill pulsegit clone --depth 1 https://github.com/duthaho/skillhubWrote 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/duthaho/skillhub/pulse)<a href="https://agentmods.dev/skills/duthaho/skillhub/pulse"><img src="https://agentmods.dev/badge/skills/duthaho/skillhub/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.00156 | $0.02259 |
| Opus 5 | $0.00078 | $0.01130 |
| Sonnet 5 | $0.00031 | $0.00452 |
| Haiku 4.5 | $0.00016 | $0.00226 |
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 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pulse — community-pulse research
/pulse <topic> [window/flags in plain language]
Answer one question: what is the community actually saying about this topic right now, and what's resonating? You ground every claim in a real source and rank by real engagement — not by what a search engine's editors surfaced.
Inputs
- Topic (required): a person, product/company, project/repo, or concept/event.
- Window (optional, plain language): default last 30 days. Honor overrides like "last week", "past 6 months", "this year". Record the resolved window.
- Any other plain-language steering ("focus on Reddit", "ELI5", "just the drama").
Step 0 — Resolve scope (ask only if genuinely ambiguous)
Run immediately for clear topics. Ask 1–2 quick questions only if:
- the name maps to multiple plausible entities (e.g. a common name, an ambiguous product), or
- there's no obvious angle and the result would likely research the wrong thing.
Otherwise proceed and state your assumptions in the brief header.
Auto-detect the topic type and weight sources accordingly:
| Detected type | Source emphasis |
|---|---|
| Person (dev/tech) | GitHub (velocity) + Hacker News + web + Reddit |
| Person (non-tech) | Web + Reddit (skip/deprioritize GitHub) |
| Product / company | Reddit + web + Hacker News (GitHub if it's a tool) |
| Project / repo / tool | GitHub + Hacker News + Reddit + web |
| Concept / event | Web + Hacker News + Reddit (skip GitHub) |
Do light entity resolution first when useful (e.g. the canonical subreddit, the
GitHub owner/repo or username, the official site) so sub-agents search the right
handles rather than guessing.
Step 1 — Fan out: parallel source sub-agents
Spawn the relevant source sub-agents concurrently (one message, multiple Agent
calls). Skip sources the topic type deprioritizes. Give each the topic, resolved
entities, and the time window. Each sub-agent must return structured findings:
for every item — title, url, source, engagement (the raw metric + its kind),
date, and a 1–2 sentence snippet. Then it deepens its top 2–3 items
(below). Each gathers ~8–10 candidates before deepening.
What ships with it
2 files 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 · 176 lines · 156 tokens per session scan A f6d5af0e6e67
pulse is a skill published in the GitHub repository duthaho/skillhub (9 stars, last pushed 10d ago), licensed MIT. It adds 156 tokens to every session and 2,259 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
auto-loop
TDD-based autonomous development loop with checkpoint recovery and observability changelog.
hook-template
Generate hook script from template. Use when adding a new hook, wiring a PreToolUse/PostToolUse/Stop/Notification hook, or scaffolding hook config for settings.json.
agent-check
Validate custom agent file format and structure. Use after creating or editing an agent, before committing agent changes, or when an agent fails to load.
skill-check
Validate skill/command file format and structure. Use after creating or editing a skill, before committing skill changes, or when a skill fails to load or trigger.
agent-template
Generate custom agent from template. Use when creating a new subagent from scratch, or scaffolding an agent file with correct frontmatter.
session-relay
Continue real repository work between Claude Code, Codex CLI, and Grok Build with a privacy-bounded, drift-aware handoff packet. Use for cross-vendor takeover, context-limit checkpoints, multi-hop Claude→Codex→Grok relays, or receiving an existing Director packet. Use native resume commands for same-CLI history; never…