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/muhammademanaftab/pulse/setupnpx skills add muhammademanaftab/pulse --skill setupgit clone --depth 1 https://github.com/muhammademanaftab/pulseWhat 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.00058 | $0.01053 |
| Opus 5 | $0.00029 | $0.00526 |
| Sonnet 5 | $0.00012 | $0.00211 |
| Haiku 4.5 | $0.00006 | $0.00105 |
Grade B, and why
setup 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Never hand-edit `~/.claude/settings.json` or `~/.pulse/config.yaml`; `install.py` How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pulse setup (agent-driven)
Take the user from a fresh clone to: capture live, daily notes configured, a first
note produced, and (optionally) a nightly routine. You run the mechanical work via
skills/setup/install.py; never hand-edit the user's settings.json or config.yaml.
Run everything from the repo root. Do the phases in order.
Phase 1: Capture
-
Say what will happen in one sentence, then run:
python3 skills/setup/install.py -
If it prints the Convex login commands (no deployment yet), have the user run them in their terminal (the
!prefix runs in this session), then re-run the script:! cd convex-backend && npx convex login ! cd convex-backend && npx convex dev --once --dev-deployment cloudThe second asks them to pick a team and name the project (suggest
pulse). -
When it finishes (creds written, hook installed, probe verified), tell them: capture is live, every Claude Code turn now records to their Convex, silent, logs at
~/.pulse/capture.log.
Phase 2: Daily notes
-
Ask where notes should live: offer to create
~/pulse-notes, or take a path they give. Then run (add--createwhen making a new repo):python3 skills/setup/install.py notes --repo <path> --createThis git-inits the repo, auto-detects their timezone, and writes
~/.pulse/config.yaml. Confirm the detected timezone with them; pass--timezone <IANA>if wrong. -
Produce a first note as a preview: follow
skills/digest/SKILL.mdfor the most recent day with data, but stop after the gates. Do NOT push or mark rows processed (the routine owns that). Show the user the note path.If
digest.py fetchreturnsevent_count0 (brand-new user, nothing captured yet), tell them plainly: notes appear once they've used Claude Code, and they can run the digest later. Do not treat this as an error.
Phase 3: Nightly routine (optional)
- Ask if they want notes built automatically every night (works with their machine
off). If yes, walk them through creating the claude.ai routine, telling them the
exact value for each field. Use
routines/README.mdas the source; the fields:
What ships with it
3 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 · 92 lines · 58 tokens per session scan B 5ce11dd70752
setup is a skill published in the GitHub repository muhammademanaftab/pulse (9 stars, last pushed 3d ago), licensed MIT. It adds 58 tokens to every session and 1,053 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
wiki-retrieve
Build and query a vault-local contextual BM25 retrieval index with optional multilingual Nomic cosine reranking; use for retrieve, hybrid retrieval, BM25, rerank, contextual retrieval, chunk search, vault search, semantic search, find relevant passages, or retrieval diagnostics. Derived caches stay under .vault-meta…
wiki
Initialize, adopt, and route work for a separate Obsidian knowledge vault through the portable claude-obsidian core. Use for vault setup, scaffolding, workspace selection, cross-project configuration, or choosing the correct wiki sub-skill. Triggers: /wiki, set up wiki, scaffold vault, create knowledge base, adopt…
defuddle
Plan and, with explicit network consent, use an optional external Defuddle cleaner to extract article-like HTTPS pages as Markdown. Use for defuddle, clean this URL, strip page clutter, readable Markdown from a web page, or preparing a web source for later wiki ingestion.
obsidian-markdown
Explain, draft, or validate Obsidian Flavored Markdown syntax: properties, wikilinks, embeds, callouts, tags, comments, highlights, block references, math, and Mermaid. Use when the user explicitly requests Obsidian note formatting or syntax help, not for general Markdown or broad vault operations.
wiki-fold
Create a bounded, extractive, structurally idempotent rollup of recent Obsidian wiki log entries, with dry-run preview by default and one optional transaction apply. Use for manual log compression without modifying child pages. Triggers: fold the log, run a fold, run wiki-fold, log rollup, roll up log entries, commit…
wiki-mode
Read or configure the vault filing methodology and suggest destinations for planned knowledge creation under Generic, LYT, PARA, or Zettelkasten. Use for wiki mode, methodology mode, what is my vault mode, set vault mode, switch to PARA, use LYT, Zettelkasten setup, change mode, configure mode, or methodology routing.…