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 e1024kb/wise-claude --skill wise-ticketsgit clone --depth 1 https://github.com/e1024kb/wise-claudeWrote 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/e1024kb/wise-claude/wise-tickets)<a href="https://agentmods.dev/skills/e1024kb/wise-claude/wise-tickets"><img src="https://agentmods.dev/badge/skills/e1024kb/wise-claude/wise-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/e1024kb/wise-claude/wise-tickets"><img src="https://agentmods.dev/badge/skills/e1024kb/wise-claude/wise-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.00224 | $0.02941 |
| Opus 5 | $0.00112 | $0.01470 |
| Sonnet 5 | $0.00045 | $0.00588 |
| Haiku 4.5 | $0.00022 | $0.00294 |
Grade A, and why
wise-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 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.
How it starts
The opening of the file, as written. The whole thing — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wise-tickets - tickets that read like tickets, not plans
Why this skill exists
A ticket generated straight from a work session reads like the work session: an exhaustive implementation plan with file lists, code snippets, and step-by-step prose. That is a Claude Code plan, not a ticket. A ticket is a contract between humans: what we want, why, where it stops, and how we know it's done - skimmable in a minute by a PM, a reviewer, or the engineer who picks it up in three weeks. This skill is the standing contract for every ticket written on the user's behalf: the section shape, the altitude, the breakdown rules, and the estimation link.
This skill composes with two siblings:
wise-human-writinggoverns voice and markup - business-level language, no ASCII diagrams, native markup per tracker, no long dashes. Apply it to every sentence of the ticket.wise-estimationgoverns the per-ticket number - the Fibonacci 0.5 → 13 SP scale and the "> 8 SP is a research ticket" rule.
wise-tickets governs everything those two don't: the structure,
the scope discipline, and how large work becomes several tickets.
Two ways this skill runs
- Standing reference (the main mode). Consult these rules
automatically whenever creating, editing, updating, or splitting a
ticket in any tracker or tracker-like system. The skill does the
full job, reads and writes included: use whatever tracker tooling
the session has - an MCP server (Jira, Linear, Asana, …), a CLI
(
jira,linear,gh issue,glab issue), or a raw API - to fetch, create, and update the tickets it shapes. When no tracker tooling is reachable, say so and hand back the drafted content instead of guessing at a write path. - Slash restructure -
/wise-tickets [<ticket-ref or draft>]. The user points at an existing ticket (a key, a URL, a pasted draft, a file) and gets back a version restructured into the canonical shape below. By default this returns text and stops; when the user asks to apply it ("update the ticket", "apply this"), write the restructured version back to the tracker with the same tooling.
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 · 248 lines · 224 tokens per session scan A be58c29de293
wise-tickets is a skill published in the GitHub repository e1024kb/wise-claude (4 stars, last pushed yesterday), licensed MIT. It adds 224 tokens to every session and 2,941 once invoked, about $0.0011 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
tackle-issue
Start-of-work triage in this monorepo. Trigger on: a GitHub issue number ("tackle issue 99", "work on #42", bare #N), pasted proposal/spec text ("investigate this", "pressure-test this", "scope this"), or picker phrasing ("tackle the next issue", "what should I work on"). Read-only investigation that tries to falsify…
stale-proposals
Audit this repository's local proposal queue for stale entries: proposals still marked proposed, deferred, or accepted even though the work already shipped, plus old proposals whose subject has become inert. Reconcile proposals against plugin changelogs and first-parent Git history, automatically resolve only…
add-source
Interactively add a new source to feed-sources.md with type inference, https and name-uniqueness validation, and category checking against feed-categories.md. Appends a formatted row to the Active Sources table. Invoke with /feed-hermit:add-source.
source-scout
Gap-driven discovery of new RSS/web sources for feed-sources.md. Interactive runs WebFetch-verify candidates and auto-add them; --scheduled runs queue unverified candidates for operator review (no WebFetch, per the domain-allowlist rule). Complements source-health (removal) with discovery (addition). Invoke with…
plan-to-tasks
Transform a plancreation planv{N}.md into a structured tasks.yaml + per-WP workpackages/.yaml using parallel Sonnet sub-agents. Use after plan-creation finishes when you need execution-friendly task structure.
debt-ops-add
Register a deferred decision in the tech-debt registry. Trigger by judgment, not a marker scan, whenever a future reader would ask "why this way?": an unmade decision, stub, loosened type, bypassed check, swallowed error, a default picked "for now", or a TODO/FIXME/HACK/XXX marker. Trigger immediately whenever you…