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 jscraik/Agent-Skills --skill he-phase-heartbeatgit clone --depth 1 https://github.com/jscraik/Agent-SkillsWrote 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/jscraik/agent-skills/he-phase-heartbeat)<a href="https://agentmods.dev/skills/jscraik/agent-skills/he-phase-heartbeat"><img src="https://agentmods.dev/badge/skills/jscraik/agent-skills/he-phase-heartbeat/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/jscraik/agent-skills/he-phase-heartbeat"><img src="https://agentmods.dev/badge/skills/jscraik/agent-skills/he-phase-heartbeat.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.00070 | $0.01296 |
| Opus 5 | $0.00035 | $0.00648 |
| Sonnet 5 | $0.00014 | $0.00259 |
| Haiku 4.5 | $0.00007 | $0.00130 |
Grade A, and why
he-phase-heartbeat 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 8d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HE Phase Heartbeat
Philosophy
Compatibility entrypoint for older $he-phase-heartbeat requests. Use the
same safety model as he-phase-work: a heartbeat can wake the thread, but it
does not authorize implementation, staging, commits, Linear updates, or closure.
When to Use
- The user asks for a phase heartbeat, recurring phase work, or a 10 minute continuation loop for an already-approved plan, issue, or PR.
- The request needs active-phase selection, collector/live-state evidence, review gates, and an explicit stop rule before commit or tracker updates.
When Not to Use
- Use plain reminders for lightweight nudges that do not execute phases.
- Use
he-workfor a single bounded implementation with no recurrence. - Use
he-planorhe-specif the plan or phase sequence is not approved.
Inputs
Approved plan path, target issue or PR, workspace, branch and dirty state, active phase, validation command, heartbeat authority, staging authority, Linear authority, stop condition, and collector or provenance evidence when cited.
Outputs
Return schema_version: 1, selected_stage: he-phase-work,
compatibility_source: he-phase-heartbeat, target, heartbeat id or blocker,
active phase, live-state status, validation outcomes, slack_policy,
stop_rule_status, and next_safe_action.
Procedure
Apply the context-disposition policy: move important still-valid context to references, and intentionally discard stale, duplicated, unsafe, superseded, or low-signal text.
- Confirm the approved plan path, target issue/PR, workspace, branch, dirty state, active phase, validation command, and stop condition.
- Reuse an existing matching 10 minute
he-phase-work; create one only when automation authority is explicit. - Check collector or live-state evidence. If evidence is stale, missing, or
unredacted, set
slack_policy: blockedand stop. - Select only the active approved phase and run the phase gate contract.
- Delegate the active implementation slice to
he-workonly when edit authority and validation route are clear. - Stop before staging, commit, merge, review-thread resolution, Linear closure, deploy, or destructive cleanup unless separately approved.
What ships with it
5 files 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.
- 8d ago First seen · 129 lines · 70 tokens per session scan A 35e2488be9fe
he-phase-heartbeat is a skill published in the GitHub repository jscraik/Agent-Skills (8 stars, last pushed 10d ago), licensed Apache-2.0. It adds 70 tokens to every session and 1,296 once invoked, about $0.0003 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
process-doc
Turn an operational process into a clear SOP, role model, control map, and improvement backlog.
taskuary-setup
Walk the owner through setting Taskuary up - the AI brain, where work arrives, the operator documents, reports and workflows - by reading the install's real state and using the screens that already exist. Use when a task was opened as a Taskuary setup walkthrough.
epic-lead
Use when delivering one approved Kanban EPIC through governed integration, review, and handoff.
teamlead
Use at the START of ANY code task — write/edit/refactor/read code, feature, bug-fix, migration, code investigation. The main thread acts as team-lead, NOT implementer — it delegates work to subagents and surfaces only decisions and results, keeping the main chat clean.
knbn
Alias for the kanban skill. Use when the user invokes or refers to Kanban as "knbn".
foreman-to-issues
Break an approved PRD into small, dependency-ordered, vertically-sliced implementation issues written as local files in the Foreman feature directory. Each issue ships a runnable acceptance check and a declared file footprint. No GitHub, no live quizzing of the user — emits files matching Foreman's issue schema with…