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/bind/skillz.sh/linear-milestones-readnpx skills add Bind/skillz.sh --skill linear-milestones-readgit clone --depth 1 https://github.com/Bind/skillz.shWrote 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/bind/skillz.sh/linear-milestones-read)<a href="https://agentmods.dev/skills/bind/skillz.sh/linear-milestones-read"><img src="https://agentmods.dev/badge/skills/bind/skillz.sh/linear-milestones-read.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.00017 | $0.00384 |
| Opus 5 | $0.00009 | $0.00192 |
| Sonnet 5 | $0.00003 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
linear-milestones-read 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 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.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 4d ago First seen · 51 lines · 17 tokens per session scan A a51b3eb81528
linear-milestones-read is a skill published in the GitHub repository Bind/skillz.sh (5 stars, last pushed 7mo ago), with no licence file. It adds 17 tokens to every session and 384 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-08-31.
Other skills, from other repositories
agtx-sweep
Sweep this conversation into agtx tasks and push them to the kanban board. Use when the user wants to capture, decompose, or hand off conversation results to the agtx board.
at-zentao
Handle ZenTao (禅道) Bugs and Tasks end to end, including updating or writing back an item after code changes, managing Task status and hours, and reading linked Stories. Use for referenced ZenTao items, requirements, status changes, time entries, or post-implementation synchronization.
openspec-bulk-apply-change
Use when multiple active OpenSpec changes should be applied concurrently in isolated worktrees with delegated verification and no merge.
armada-gate
Run an evidence-gate checklist for each success criterion in the current phase. Use when checking if a phase is complete before marking it passed.
to-tickets
Break a spec or plan into trackable GitHub issues. Use when a plan/spec needs splitting into work items, or the task mentions "tickets", "工单", "break into issues", "分解任务". Emits one issue per independently completable unit with acceptance criteria.
triage
Label-based issue triage workflow. Use when a batch of issues needs sorting by priority/type, or the task mentions "triage", "分流", "prioritize issues", "label". Pulls issues, classifies them, and applies labels/assignees via gh.