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.
git clone --depth 1 https://github.com/Floka-as/floka-marketplaceWrote 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/commands/floka-as/floka-marketplace/pulse)<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.
<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>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.00027 | $0.01308 |
| Opus 5 | $0.00014 | $0.00654 |
| Sonnet 5 | $0.00005 | $0.00262 |
| Haiku 4.5 | $0.00003 | $0.00131 |
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.
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
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.
- 12d ago First seen · 152 lines · 27 tokens per session scan A dba44a3d47b2
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.
Other commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
handoff
Export a Waybill Bundle by default, or import one when requested.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.