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 thcjp/hermes-skills --skill linear-autopilotgit clone --depth 1 https://github.com/thcjp/hermes-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/thcjp/hermes-skills/linear-autopilot)<a href="https://agentmods.dev/skills/thcjp/hermes-skills/linear-autopilot"><img src="https://agentmods.dev/badge/skills/thcjp/hermes-skills/linear-autopilot/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/thcjp/hermes-skills/linear-autopilot"><img src="https://agentmods.dev/badge/skills/thcjp/hermes-skills/linear-autopilot.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.00000 | $0.02039 |
| Opus 5 | $0.00000 | $0.01019 |
| Sonnet 5 | $0.00000 | $0.00408 |
| Haiku 4.5 | $0.00000 | $0.00204 |
Grade A, and why
linear-autopilot 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 9d 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 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.
- 9d ago First seen · 283 lines · 0 tokens per session scan A fe775953b281
linear-autopilot is a skill published in the GitHub repository thcjp/hermes-skills (1 stars, last pushed 18d ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 2,039 tokens. 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
github-issues
Create, list, view, and manage GitHub issues using the gh CLI.
linear
Manage Linear issues, projects, and cycles via the Linear GraphQL API.
frappe-impl-workflow
Use when implementing document Workflows, approval chains, or state-based transitions in Frappe. Prevents stuck documents from missing transitions, broken approval chains, and permission errors on workflow actions. Covers Workflow DocType, Workflow State, Workflow Action, transition rules, allowed roles, conditions…
cross-functional-alignment
Bring engineering, design, research, marketing, and sales onto the same page and keep them there. Covers alignment levels, RACI clarity, and continuous maintenance. Use when teams have different understandings of what's being built, cross-team dependencies are causing problems, or alignment keeps breaking down.
working-with-engineering
Partner with engineering as a collaborator, not a ticket-writer. Covers communication norms, technical empathy, scope negotiation, and building mutual trust. Use when PM-engineering relationships feel transactional, technical decisions are made without product input, or scope conversations become adversarial.
communicating-decisions
Communicate product decisions so teams understand not just what was decided but why. Covers framing, transparency about trade-offs, and handling disagreement gracefully. Use when decisions aren't sticking, teams are relitigating past calls, or when stakeholders feel left out.