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 jamestexas/agents --skill linear-escalation-triagegit clone --depth 1 https://github.com/jamestexas/agentsWrote 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/jamestexas/agents/linear-escalation-triage)<a href="https://agentmods.dev/skills/jamestexas/agents/linear-escalation-triage"><img src="https://agentmods.dev/badge/skills/jamestexas/agents/linear-escalation-triage/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/jamestexas/agents/linear-escalation-triage"><img src="https://agentmods.dev/badge/skills/jamestexas/agents/linear-escalation-triage.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.00060 | $0.02253 |
| Opus 5 | $0.00030 | $0.01126 |
| Sonnet 5 | $0.00012 | $0.00451 |
| Haiku 4.5 | $0.00006 | $0.00225 |
Grade A, and why
linear-escalation-triage 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.
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.
- 8d ago First seen · 184 lines · 60 tokens per session scan A 646d9fb1a66f
linear-escalation-triage is a skill published in the GitHub repository jamestexas/agents (2 stars, last pushed 6d ago), with no licence file. It adds 60 tokens to every session and 2,253 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-08-31.
Other skills, from other repositories
triage
A structured issue-triage process that moves issues and, where configured, pull requests through classification and status steps. Triage means deciding what a report is, whether more information is needed, and who should handle it.
plan-to-tickets
Use when a large plan, PRD, feature, refactor, research plan, or multi-step coding task must be split into small ready-for-agent tickets with acceptance criteria, verification commands, blockers, and vertical tracer-bullet slices. Do not use for small tasks that should be implemented directly, single-bug fixes, or…
to-tickets
A method for turning a plan, specification, or conversation into small work tickets that each deliver a complete, testable slice of functionality. Each ticket records which other tickets must be finished first.
to-spec
A method for turning the current conversation and codebase understanding into a detailed software specification, then publishing it as an issue in the project’s issue tracker. An issue tracker is a tool for recording and managing development work.
alive:create-walnut
Something new is emerging. A venture, an experiment, a person entering the orbit, a life area getting serious. It needs its own walnut — its own identity, history, and future. Scaffolds the full structure, maps existing context sources, and optionally migrates files across.
alive-bundle
Create, manage, and graduate bundles -- the unit of focused work within a walnut.