pulse

pulse is a command for Claude Code from Floka-as/floka-marketplace. It costs 27 tokens per session (1,308 once invoked), scanned A, original, MIT.

A development health report built from a repository’s Git history and current worktrees. It summarizes delivery activity, branch condition, release patterns, and ongoing work.

In plain words
What is it for?
Use it to review recent commits, active development days, feature and fix patterns, release frequency, merge timing, and worktree status.
Why use it?
It turns scattered version-control activity into a single view of how development is progressing. This helps reveal stalled branches, uneven shipping, or changes in team activity.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: positional $N argument.

Part of the forge plugin — 1 skill, 6 commands shipped together

Good fit Use it to review recent commits, active development days, feature and fix patterns, release frequency, merge timing, and worktree status.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/floka-as/floka-marketplace/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.

Clone the repo
git clone --depth 1 https://github.com/Floka-as/floka-marketplace

Made for: Claude Code.

Or install forge, the plugin that ships this one along with the rest of its 1 skill, 6 commands.

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 pulse

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/floka-as/floka-marketplace/pulse"><img src="https://agentmods.dev/badge/commands/floka-as/floka-marketplace/pulse.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,308 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00027 $0.01308
Opus 5 $0.00014 $0.00654
Sonnet 5 $0.00005 $0.00262
Haiku 4.5 $0.00003 $0.00131

Measured 12d ago against content hash dba44a3d47b2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, 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 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.

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.

forge/commands/pulse.md · 152 lines

How it starts

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

Forge: Pulse

Generate a development health report — not a build command, a state observation tool. Think DORA metrics but qualitative, tailored to a repo using the Forge workflow.

Process

Run the following data collection steps, then generate an HTML report.

1. Git Velocity (last 30 days)

# Commits per week
git log --since="30 days ago" --pretty=format:"%ad" --date=format:"%Y-W%V" | sort | uniq -c

# Feat/fix/chore ratio
git log --since="30 days ago" --pretty=format:"%s" | awk '{print $1}' | sort | uniq -c | sort -rn

# Active days
git log --since="30 days ago" --pretty=format:"%ad" --date=short | sort -u | wc -l

# Commits per active day
echo "total_commits / active_days"

2. DORA-ish Metrics (qualitative)

Calculate these from git history:

Deployment Frequency:

# Count releases/deploys (release tags + deploy-marker commits)
git log --since="30 days ago" --oneline --grep="release:" --grep="deploy:" | wc -l
git tag --sort=-creatordate | head -10

Lead Time to Merge:

# For each merged branch in last 30 days:
# Time from first commit on branch → merge to main
# Use: git log --merges --since="30 days ago" then for each, find the branch's first commit date

Change Failure Rate:

# Reverts and hotfixes as % of total
git log --since="30 days ago" --oneline --grep="Revert" --grep="hotfix" --grep="revert" -i | wc -l

Time to Restore:

# Time between a revert commit and the fix commit (manual assessment from git log)

3. Branch Health

# All local branches with last commit date
git for-each-ref --sort=-committerdate refs/heads/ --format='%(committerdate:short) %(refname:short)'

# Worktrees
git worktree list

# Merged vs unmerged (against the project's default branch — main, master, develop, etc.)
git branch --merged | wc -l
git branch --no-merged | wc -l

# Stale remote branches (>30 days, no open PR)
git for-each-ref --sort=committerdate refs/remotes/origin/ --format='%(committerdate:short) %(refname:short)' | head -20

Read the full file on GitHub · 152 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 · 152 lines · 27 tokens per session scan A dba44a3d47b2

Subscribe to this mod's changes

pulse is a command published in the GitHub repository Floka-as/floka-marketplace (7 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 1,308 once invoked, about $0.0001 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.