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-linear-plangit 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-linear-plan)<a href="https://agentmods.dev/skills/jscraik/agent-skills/he-linear-plan"><img src="https://agentmods.dev/badge/skills/jscraik/agent-skills/he-linear-plan/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-linear-plan"><img src="https://agentmods.dev/badge/skills/jscraik/agent-skills/he-linear-plan.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.00049 | $0.02570 |
| Opus 5 | $0.00024 | $0.01285 |
| Sonnet 5 | $0.00010 | $0.00514 |
| Haiku 4.5 | $0.00005 | $0.00257 |
Grade A, and why
he-linear-plan 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harness Engineering Linear Plan
Philosophy
Linear is execution state; .harness is cognition and proof. Turn approved HE
cognition into the smallest useful Linear execution slice and make live mutation
status explicit. A local plan must never masquerade as a created issue, bug,
milestone, parent tracker, or live project mutation.
Decision records are upstream cognition, not backlog. When source artifacts imply architecture-shaping, governance-defining, moat-critical, or expensive-to-reverse decisions, preserve or request compressed ADR evidence before routing execution. Do not convert missing ADR reasoning into Linear issue volume.
When to Use
Use when approved .harness cognition needs Linear routing: destination,
existing project match, milestone/parent shape, sub-issues, dependencies, eval
gates, labels, priority, project/cycle justification, and human/agent route.
Also use when an HE prompt asks to convert ADRs, reframe programs, strategy, or
core invariants into a small Linear execution plan.
When Not to Use
Do not generate strategy, reframe programs, specs, implementation plans, implementation work, architecture reviews, eval closure, unfiltered backlog, or ADR spam. If required decision evidence is absent, route to the appropriate upstream cognition step or mark the Linear plan blocked instead of inventing architecture memory inside Linear.
Inputs
Approved .harness/** cognition, repo scope, source-prompt coverage evidence,
ADR readiness evidence, Linear identifiers when known, project/cycle evidence,
mutation approval state, and bug reproduction evidence.
Outputs
Write a dated .harness/linear/**-linear-plan.md artifact or return
needs_human_triage, Later, or Do Not Create. Ready-to-create payloads
stay unapplied unless live mutation is explicitly approved.
Always include schema_version: 1, selected_stage: he-linear-plan, evidence
traceability, Target Linear Destination, Existing Project Match,
Now/Next/Later/Do Not Create, decision_artifact_status,
source_prompt_family_status when source-prompt preservation is in scope,
linear_mutation_status, required_confirmation when needed, and
live_linear_blocker when expected live tracking is blocked. Include
git_staging_status and staged_paths when writing local Linear artifacts.
Bug work includes
issue_type: bug, repro, expected/actual behavior, affected surface, severity,
and validation evidence.
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 · 235 lines · 49 tokens per session scan A 96c369bdd127
he-linear-plan is a skill published in the GitHub repository jscraik/Agent-Skills (8 stars, last pushed 10d ago), licensed Apache-2.0. It adds 49 tokens to every session and 2,570 once invoked, about $0.0002 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…