pulse

A project-momentum check that examines your Git history and project notes to assess whether work is still moving forward.

In plain words
What is it for?
Use it to review project momentum, spot signs that an idea is losing novelty, and record a decision about what to do next.
Why use it?
It helps when you feel stuck by turning recent development activity into a recommendation to continue, change direction, or pause the project.

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/pyros-projects/limitless/pulse
Any agent
npx skills add pyros-projects/limitless --skill pulse
Clone the repo
git clone --depth 1 https://github.com/pyros-projects/limitless

Made for: Claude Code, Codex.

Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,289 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00063 $0.04289
Opus 5 $0.00032 $0.02145
Sonnet 5 $0.00013 $0.00858
Haiku 4.5 $0.00006 $0.00429

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

Security

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

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.

plugins/pyro-kit/skills/pulse/SKILL.md · 415 lines

How it starts

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

!if [ -f .pyro/state.md ]; then cat .pyro/state.md; else echo "NO_PROJECT_STATE"; fi !if [ -f "${CLAUDE_PLUGIN_ROOT}/scripts/git-activity.sh" ]; then bash "${CLAUDE_PLUGIN_ROOT}/scripts/git-activity.sh" 30; else echo "NO_GIT_ACTIVITY"; fi

Persona

Act as a momentum analyst. You compute, never ask. When a developer invokes /pulse, your first output is always the complete dashboard — synthesized from git data, state, and codebase structure. You make a specific recommendation backed by evidence. You don't treat the three paths as equal; you have a view and you state it. You respect "not now" without commentary.

Input: $ARGUMENTS

Interface

fn analyze()        // Gather git metrics, read state, read spark — all before first output
fn dashboard()      // Render the full momentum dashboard using reference/dashboard-format.md
fn recommend()      // Derive a specific push/pivot/shelve recommendation with cited evidence
fn record(decision) // Append to .pyro/pulse-log.md, update .pyro/state.md

Constraints

Constraints { require { First output is ALWAYS the complete dashboard — never a question, never a clarifying ask. Original spark MUST be quoted verbatim in blockquote format — no paraphrasing. All three paths (push/pivot/shelve) must be pre-built with concrete first steps before presenting. Make a SPECIFIC recommendation — label it clearly, cite the evidence behind it. Handle gracefully: no state, no spark, no git, fewer than 5 commits. Use Bash tool to run git-activity.sh if shell preprocessor output is NO_GIT_ACTIVITY. Append to .pyro/pulse-log.md on every completed pulse — never overwrite. Respect "not now" — record the non-decision, do not nag or re-propose. } never { Ask "how do you feel about the project?" or any open-ended sentiment question. Paraphrase the original spark — always verbatim or label as inferred. Present three equal options without a recommendation. Overwrite .pyro/pulse-log.md — it is append-only. Re-compute paths after developer states preference — they're already built. Nag after "not now" — record it and stop. } }

Read the full file on GitHub · 415 lines

Files

What ships with it

1 file 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.

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 · 415 lines · 63 tokens per session scan A b354b29c37c6

Subscribe to this mod's changes

pulse is a skill published in the GitHub repository pyros-projects/limitless (9 stars, last pushed 20d ago), licensed MIT. It adds 63 tokens to every session and 4,289 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

omh-agent-board

This is a Hermes-native agent-board workflow skill.

rlaope/oh-my-hermes · 67 tokens

omh-feedback-triage

This is a Hermes-native feedback-triage workflow skill.

rlaope/oh-my-hermes · 64 tokens

triage-sweep

Backfill labels across oh-my-hermes issues and pull requests. Run manually to sweep everything currently unlabeled, or pass a number to triage one item. Use when issues and PRs have accumulated without labels, after adding a new label to .github/labels.yml, or before a release when the backlog needs to be readable by…

rlaope/oh-my-hermes · 74 tokens

team-workflow

Design the team's operating rhythm — task management, collaboration rituals, and tooling. Use when the day-to-day cadence needs structure. For a time-boxed sprint, use design-sprint-plan.

Owl-Listener/designer-skills · 43 tokens

meeting-minutes

Turn a meeting transcript, notes, or conversation into collision-safe, source-linked minutes in meetings/YYYY-MM-DD-slug.md. Use for project meeting records, attendance, discussion, stated information, decisions, action candidates, and open questions. Saving minutes never changes PROJECT.md, decisions/, or TASKS.md…

AlpacaLabsLLC/skills-for-architects · 72 tokens

implement

End-to-end workflow for taking MCP work items from backlog to merged PR. Handles git branching, schema-driven planning, implementation, independent review, and PR creation. Composes spec-quality, review-quality, and schema-workflow skills into a single pipeline. Use when a user says "implement this", "work on this…

jpicklyk/task-orchestrator · 101 tokens