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/snowflake-labs/cocoplus/pulsenpx skills add Snowflake-Labs/cocoplus --skill pulsegit clone --depth 1 https://github.com/Snowflake-Labs/cocoplusWrote 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/snowflake-labs/cocoplus/pulse)<a href="https://agentmods.dev/skills/snowflake-labs/cocoplus/pulse"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/pulse.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.00010 | $0.00297 |
| Opus 5 | $0.00005 | $0.00148 |
| Sonnet 5 | $0.00002 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00030 |
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 yesterday.
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.
What it actually says
Your objective is to implement $pulse.
Before proceeding, verify that .cocoplus/ exists. If not, output: "CocoPlus not initialized in this directory. Run $pod init to begin." Then stop.
Read .cocoplus/modes/pulse.on and .cocoplus/pulse/config.json when present. Report enabled state, interval, watched artifacts, last pulse, and next expected progress check.
Available subcommands: $pulse on, $pulse off, $pulse status, $pulse configure.
Anti-Rationalization
| Shortcut / Temptation | Why It Fails |
|---|---|
| Treat the skill as complete because the file exists | Skill contracts must describe observable behavior and verification, not just command names. |
| Skip artifact and safety checks for a small command | Small commands still mutate state or guide execution; preserve the same gates. |
Exit Criteria
- Command behavior matches the owning feature contract.
- Required reads, writes, and user-visible outputs are described.
- Safety, governance, and artifact constraints are preserved.
- Missing state produces a clear, non-destructive result.
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.
- yesterday First seen · 33 lines · 10 tokens per session scan A bcd4b56d39af
pulse is a skill published in the GitHub repository Snowflake-Labs/cocoplus (720 stars, last pushed 2d ago), licensed MIT. It adds 10 tokens to every session and 297 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-09-03.
Other skills, from other repositories
glyph
Render an answer as ASCII art plus semantic emojis inline, right now, with no setup questions. Use for a fast visual take on status, comparisons, trade-offs, architecture, or any ad-hoc 'show me X visually' ask. For a full multi-artifact plan playground, use visualize-plan instead.
screenpipe-api
Query the user's local and synced-device Screenpipe data via the REST API at localhost:3030. Use for screen activity, meetings, apps, productivity, other-device or cross-device history, media export, retranscription, or connected services.
markedit-tools
Provides tools for managing MarkEdit, a macOS markdown editor.
differed-task-execution
Delays execution of a task until a specified time or after a duration. Use when the user asks to run something later, in X minutes/hours, at a specific time, schedule a command, or defer work to a future point.
instructor-release
Prepare and execute a new InstructorPHP version release. Use when asked to cut a release, prepare release notes, run release QA, create a release epic and tasks in bd, verify changed packages since the last tag, run curated live examples, publish via scripts/release/publish-ver.sh, or prepare the launch announcement.
daily-life-discovery
Guide a consent-based conversation that helps a person discover how an AI agent could improve their day-to-day life: routines, friction, attention, decisions, relationships, learning, and small experiments. Use when someone asks for a daily check-in, wants the agent to learn how they work, says "grill me," wants a…