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 Nunchi-trade/agent-cli --skill pulsegit clone --depth 1 https://github.com/Nunchi-trade/agent-cliWrote 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/nunchi-trade/agent-cli/pulse)<a href="https://agentmods.dev/skills/nunchi-trade/agent-cli/pulse"><img src="https://agentmods.dev/badge/skills/nunchi-trade/agent-cli/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/skills/nunchi-trade/agent-cli/pulse"><img src="https://agentmods.dev/badge/skills/nunchi-trade/agent-cli/pulse.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00019 | $0.00994 |
| Opus 5.5 | $0.00008 | $0.00398 |
| Sonnet 5.5 | $0.00004 | $0.00199 |
| Haiku 4.5 | $0.00002 | $0.00099 |
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 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.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- pulse — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pulse — Capital Inflow Detector
Identifies assets accelerating in capital concentration before they become crowded positions. Uses publicly available HL market data as proxy signals for institutional flow detection.
Signal Types
| Signal | Trigger | Confidence |
|---|---|---|
| IMMEDIATE_MOVER | OI +15% AND volume 5x surge | 100 |
| VOLUME_SURGE | Recent 4h volume > 3x average | 70 |
| OI_BREAKOUT | OI jumps 8%+ above baseline | 60 |
| FUNDING_FLIP | Funding rate reversal or 50%+ acceleration | 50 |
Direction Classification
Majority vote across available signals:
- Funding rate sign -> directional bias
- Price breakout direction
- Volume surge + price momentum
Quality Filters
- Erratic detection (rank bouncing -> filtered)
- Minimum 24h volume ($500K default)
- Minimum scan history for baseline (2 scans)
Usage
hl pulse once # Single scan
hl pulse run --tick 60 # Continuous (60s intervals)
hl pulse once --json # JSON output
hl pulse once --mock # Mock data
hl pulse status # Last scan results
hl pulse presets # List presets
Agent Mandate
You are the Pulse capital inflow detector. Your job is to catch capital inflow signals BEFORE the crowd. You detect timing — Radar detects setups. Together they form the APEX entry pipeline.
RULES:
- IMMEDIATE_MOVER is the only signal strong enough for standalone entry
- All other signals require Radar confirmation (score > 170)
- ALWAYS check baseline history — signals from assets with < 2 scans are unreliable
- NEVER act on erratic assets (rank bouncing between scans)
- Report direction with every signal — directionless signals are useless
Decision Rules
| Signal Type | Confidence | Standalone Entry? | Action |
|---|---|---|---|
| IMMEDIATE_MOVER | 100 | YES | Enter immediately — rare, high-conviction |
| VOLUME_SURGE | 70 | NO | Check Radar score. Enter if > 170 |
| OI_BREAKOUT | 60 | NO | Check Radar score. Enter if > 200 |
| FUNDING_FLIP | 50 | NO | Informational only — do not enter on funding alone |
| Multiple signals same asset | Varies | YES if combined > 150 | Compound conviction — enter with caution |
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.
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 · 102 lines · 19 tokens per session scan A b167c8bc8498
pulse is a skill published in the GitHub repository Nunchi-trade/agent-cli (521 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 994 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
pulse
Detects assets with sudden capital inflow via OI/volume/funding proxy signals.
hyperliquid-orders
Place, cancel and modify Hyperliquid orders correctly from the desk computer - limit and IOC (market-style) orders, take-profit and stop-loss trigger orders with grouping, client order ids, reduce-only, batch actions, price and size rounding, and how to read every response status. Write path - Execution Trader only…
desk-risk-limits
How the Risk Manager writes the desk's risk limits with the user, sizes every proposed trade from live account state and Hyperliquid's real constraints, checks the book, and issues a PASS or REJECT with exact ticket fields. Use for setting up or changing limits, sizing any trade, and answering "how's the book".
desk-strategy-lab
How the Strategist works with the user to turn their own trading idea into explicit rules, backtest it honestly on Hyperliquid candle and funding history, and paper-trade it on testnet through the desk lifecycle. Method only - the desk ships no strategies and makes no return claims. Use when the user wants to design…
hyperliquid-advanced
Less common Hyperliquid actions and their rules - dead-man's switch (scheduleCancel), TWAP orders, spot orders, expiresAfter and nonces, API wallet approval from code, sub-account and vault addressing, HIP-3 dexs, and what the desk deliberately does not do (transfers, withdrawals, builder fees, staking). Write actions…
hyperliquid-websocket
Subscribe to live Hyperliquid data over WebSocket from the desk computer - mids, order book, trades, candles, best bid/offer, and per-account fills, order updates and events - with raw JSON, Python SDK and TypeScript examples, plus how to run a supervised watch that logs to a file and alerts. Read-only. Use for…