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 skills add muhammademanaftab/pulse --skill setupgit clone --depth 1 https://github.com/muhammademanaftab/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/skills/muhammademanaftab/pulse/setup)<a href="https://agentmods.dev/skills/muhammademanaftab/pulse/setup"><img src="https://agentmods.dev/badge/skills/muhammademanaftab/pulse/setup/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.
<a href="https://agentmods.dev/skills/muhammademanaftab/pulse/setup"><img src="https://agentmods.dev/badge/skills/muhammademanaftab/pulse/setup.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00058 | $0.01053 |
| Opus 5.5 | $0.00023 | $0.00421 |
| Sonnet 5.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 1mo 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.
- 1mo 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 2d ago), licensed MIT. It adds 58 tokens to every session and 1,053 once invoked, about $0.0002 per session on Opus 5.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
apply
A browser-based job application workflow for submitting applications through services such as Ashby, Greenhouse, Lever, and Hacker News. It uses prepared candidate information, answers, job links, and cover letters.
behavior-design
Use when a goal must be converted into a repeatable behavior, cue, SOP, review cadence, and identity-aligned reinforcement.
daily-okr
Use when planning or closing a daily knowledge-compounding cycle across input, cognition, wiki, behavior, creativity, output, and feedback.
priority-dashboard
Use this to rebuild, inspect, or temporarily steer {{username}}'s current PersonalOS priority dashboard from canonical Actions, Attention Triggers, and owner context. Do NOT use it to create, complete, or independently manage tasks; use task-manager for Action and Trigger lifecycle changes.
screenpipe-api
Query the user's local and synced-device data via the screenpipe REST API at localhost:3030 — recordings, audio, UI, meetings, connected services, and memory. Use for screen activity, other-device or cross-device history, productivity, media export, connections, durable memory, or discovering and automating saved…
retro-lost
Run a retrospective for an abandoned agent session (untouched for over 24 hours, never closed with a retro): rebuild context cold from the transcript, list what was built, sort Keep/Drop/Try and file the durable parts. Use from a nightly routine or on demand. Triggers: /retro-lost, retro for an abandoned session.