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 Devin-AXIS/iPolloWork --skill linear-project-updatesgit clone --depth 1 https://github.com/Devin-AXIS/iPolloWorkWrote 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/devin-axis/ipollowork/linear-project-updates)<a href="https://agentmods.dev/skills/devin-axis/ipollowork/linear-project-updates"><img src="https://agentmods.dev/badge/skills/devin-axis/ipollowork/linear-project-updates.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.1 | $0.00026 | $0.00140 |
| Opus 5 | $0.00013 | $0.00070 |
| Sonnet 5 | $0.00005 | $0.00028 |
| Haiku 4.5 | $0.00003 | $0.00014 |
Grade A, and why
linear-project-updates 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 3d 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
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 3d ago First seen · 16 lines · 26 tokens per session scan A 149f48168678
linear-project-updates is a skill published in the GitHub repository Devin-AXIS/iPolloWork (5,383 stars, last pushed yesterday), with no licence file. It adds 26 tokens to every session and 140 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
manage-taskboard
Manage work in the native DeepSeek Harness Taskboard with exact task ids and optimistic versions. Use when an Agent must inspect project work, claim an eligible todo, record progress or blockers, verify an implementation, submit it for human review, or release its own claim; also use when a human asks how to accept…
yao-board
Kanban board and task query expert. ALWAYS invoke this skill when the user asks about boards, tasks, task status, or project progress. Do not guess task state — use this skill first.
dev-team
Simulate a collaborative dev team session where multiple role-based personas (PM, Architect, Developer, QA) respond to the same problem together in one session. Use when designing a feature, reviewing a proposal, or onboarding a new initiative and you want multi-role perspective without switching agents manually.
wayfinder
A planning skill that turns a large, unclear piece of work into a shared map of decisions in an issue tracker, then works through those decisions until the route is clear.
product-prd
A Chinese-language product-definition and requirements workflow that turns an approved idea into a product definition and a PRD, a detailed product requirements document.
triage
A workflow for sorting project issues and external pull requests through defined categories and status labels. An issue is a reported problem or request, while a pull request is a proposed code change.