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 SaikaAco/saika-hermes-skills --skill to-ticketsgit clone --depth 1 https://github.com/SaikaAco/saika-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/saikaaco/saika-hermes-skills/to-tickets)<a href="https://agentmods.dev/skills/saikaaco/saika-hermes-skills/to-tickets"><img src="https://agentmods.dev/badge/skills/saikaaco/saika-hermes-skills/to-tickets/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/saikaaco/saika-hermes-skills/to-tickets"><img src="https://agentmods.dev/badge/skills/saikaaco/saika-hermes-skills/to-tickets.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.00043 | $0.02183 |
| Opus 5 | $0.00022 | $0.01092 |
| Sonnet 5 | $0.00009 | $0.00437 |
| Haiku 4.5 | $0.00004 | $0.00218 |
Grade A, and why
to-tickets 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 12d 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Traceable To-Tickets
Lineage
This is an MIT-licensed Hermes adaptation of Matt Pocock's public
to-tickets.
The complete upstream notice is preserved in
references/third-party-notices.md.
Compile one exact, user-accepted source snapshot into an agent-sized delivery graph. Initial invocation authorizes a chat draft only.
DRAFT_READY means an honest reviewable draft exists; it does not mean
grounding is complete or authorize publication or implementation. Pending
pre-publication grounding, graph rechecks, or fresh approval may coexist with
DRAFT_READY when accepted facts already determine the safe draft shape. Use
BLOCKED when missing facts prevent an honest draft or materially change its
graph, sizing, sequencing, or safety. For decision-only decomposition, do not
block merely because later implementation details remain unknown.
Source and grounding
Accept one exact source snapshot with identifiable scope, owner, requirements,
decision/evidence handles, constraints, negatives/exceptions, out-of-scope
boundaries, observable acceptance, and required evidence. Do not infer acceptance
or current truth from an old conversation, a similarly named file, or mere
draft existence. Keep source_snapshot exactly equal to the accepted version,
revision, fingerprint, or message handle. Put drift history or missing-revision
explanations in lineage, blockers, or a separate drift field; never append
those explanations to the snapshot value.
Before slicing, inspect only current repository and record evidence needed to validate implementation-facing claims: active project/tracker policy, governing decisions and vocabulary, relevant interfaces, seams, behavior and tests, plus source negatives, exceptions, and acceptance methods. Prior exploration does not validate a specific claim. A direction to reuse an unnamed “existing seam” does not itself verify that seam.
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.
- 12d ago First seen · 213 lines · 43 tokens per session scan A 8092845f6573
to-tickets is a skill published in the GitHub repository SaikaAco/saika-hermes-skills (2 stars, last pushed 14d ago), licensed MIT. It adds 43 tokens to every session and 2,183 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-08-31.
Other skills, from other repositories
gh-issues
Triage GitHub issues, select safe candidates, implement focused fixes, open pull requests, and address actionable review feedback.
document-to-action-items
Turn documents, notes, transcripts, and meeting records into traceable action items, decisions, owners, deadlines, and follow-ups without inventing missing commitments.
github
Use GitHub CLI for repositories, issues, pull requests, reviews, CI runs, releases, and structured GitHub API queries.
kill-the-standup
Reads yesterday's Linear issues and GitHub commits for the authenticated user, formats a standup update (done / doing / blockers), and posts it to Slack. Use when asked to write a standup, generate a standup update, post to the standup channel, summarize yesterday's work, or automate the daily standup. Trigger when a…
kanban-orchestrator
Kanban orchestrator: decompose, route, verify. No executing.
hermes-kanbanize
Use when an existing conversation, plan, specification, or objective must become a Hermes-native Kanban board with verifiable work slices, real blocking edges, a clear execution frontier, and no duplicate scheduler.