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 agentmods add skills/knqiufan/pulse-line/setup-guidenpx skills add knqiufan/pulse-line --skill setup-guidegit clone --depth 1 https://github.com/knqiufan/pulse-lineWrote 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/knqiufan/pulse-line/setup-guide)<a href="https://agentmods.dev/skills/knqiufan/pulse-line/setup-guide"><img src="https://agentmods.dev/badge/skills/knqiufan/pulse-line/setup-guide.svg" alt="Measured on agentmods" 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 | $0.00039 | $0.00678 |
| Opus 5 | $0.00019 | $0.00339 |
| Sonnet 5 | $0.00008 | $0.00136 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade B, and why
setup-guide 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 4d 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.
3. Write `statusLine.command` to `~/.claude/settings.json` How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pulse Line Setup Guide
When to Use
- User asks to install or set up pulse-line
- User asks to configure or customize the status bar
- User reports the status bar is not showing
- User wants to change themes, enable/disable modules, or adjust layout
Installation
Run the following command to install and configure pulse-line:
npx -y pulse-line@latest install
This command will:
- Create the config directory at
~/.claude/pulse/ - Save default configuration to
~/.claude/pulse/config.json - Write
statusLine.commandto~/.claude/settings.json
After running, tell the user to restart Claude Code for the status bar to appear.
If Already Installed via Plugin Marketplace
The plugin automatically configures itself on the next session start via a SessionStart hook. If the status bar still doesn't appear:
- Check if
~/.claude/settings.jsoncontains:
{
"statusLine": {
"type": "command",
"command": "npx -y pulse-line@latest"
}
}
- If missing, run:
npx -y pulse-line@latest install
- Restart Claude Code.
Common Customizations
Switch Theme
npx -y pulse-line@latest theme <name>
Available themes: dark, light, cyberpunk, forest, ocean
Switch Language
npx -y pulse-line@latest language zh
Enable/Disable Modules
npx -y pulse-line@latest enable <module>
npx -y pulse-line@latest disable <module>
Available modules: model, git, workspace, context, cacheRatio, mcpStatus, accountUsage, turns, thinking, cost, duration, rateLimits, weeklyQuota, outputStyle, thirdPartyApi
Edit Full Configuration
npx -y pulse-line@latest config
Config file location: ~/.claude/pulse/config.json
Troubleshooting
Status bar not showing
- Verify
~/.claude/settings.jsonhas thestatusLinefield - Run
npx -y pulse-line@latest installto re-configure - Restart Claude Code
Icons showing as boxes or garbled characters
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.
- 4d ago First seen · 108 lines · 39 tokens per session scan B 27dee771433b
setup-guide is a skill published in the GitHub repository knqiufan/pulse-line (6 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 678 once invoked, about $0.0002 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…