Borrowing it
Nothing to install: this file belongs to sponge-b0b/Polaris. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sponge-b0b/Polaris/main/.agents/skills/to-tickets/SKILL.mdgit clone --depth 1 https://github.com/sponge-b0b/PolarisWrote 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/sponge-b0b/polaris/to-tickets)<a href="https://agentmods.dev/skills/sponge-b0b/polaris/to-tickets"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/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/sponge-b0b/polaris/to-tickets"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/to-tickets.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 89 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 237 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 541 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00039 | $0.10881 |
| Opus 5 | $0.00019 | $0.05441 |
| Sonnet 5 | $0.00008 | $0.02176 |
| Haiku 4.5 | $0.00004 | $0.01088 |
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 today.
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 — 1,106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
To Tickets
Create tracer-bullet tickets using the publication workflow below, with hard boundaries for exhaustive source coverage and independently certified proposal readiness before human approval.
This SKILL.md is the single authoritative procedure for $to-tickets. The preserved procedure later in this file remains normative for session recovery, project-delivery guards, codebase exploration, mode routing, $to-remediation-tickets, vertical slicing, user approval, Spec Branch Rule, tracker publication, native hierarchy/dependencies, ticket baseline/branch semantics, and handoff.
The hardening sections immediately below add the fresh-Spec obligation-coverage gate, independently certified proposal readiness before human approval, exact Spec provenance on ordinary tickets, conditional/deferred obligation routing, and the design-delegation guard. On conflict with older wording later in this file, these hardening sections win.
The remediation path remains owned by $to-remediation-tickets; do not replace its Root Blocker delta contract with the fresh-Spec mapping below.
Design Delegation Guard
$to-tickets decomposes a frozen implementation-ready contract. It does not design the behavior that $implement-ticket will later choose.
Before proposal-readiness certification for every software ticket set:
- require the source Spec/remediation authority to be currently implementation-ready under its own durable readiness state;
- inspect every proposed ticket for material choices left to implementation;
- apply the
AGENTS.mdmaterially-different-implementations test; - invoke
$attentionas prescribed internal composition before freezing the proposal.
For each material candidate choice classify:
Choice: <public/domain/downstream choice>
Authority: <exact source>
Disposition: frozen-upstream | semantically-equivalent-mechanic | unresolved-design
unresolved-design is never a legal ticket handoff. If two reasonable implementations could satisfy the ticket while establishing materially different public, product, domain, architecture, persistence, or downstream contracts, return the affected scope to its owning Spec/design authority rather than drafting acceptance criteria that silently delegate the choice.
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.
- today Changed · -22 lines 1690115b19d5
- 2d ago Changed · +83 lines 5bda29e53603
- 3d ago Changed · +43 lines 7184b93d65e0
- 4d ago Changed · +52 lines 3e319ae77b8a
- 7d ago Changed · +327 lines · +2 tokens per session 5604b49777bd
- 11d ago First seen · 623 lines · 37 tokens per session scan A 7c1c3d109601
to-tickets is a skill published in the GitHub repository sponge-b0b/Polaris (4 stars, last pushed today), licensed Apache-2.0. It adds 39 tokens to every session and 10,881 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.