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-remediation-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-remediation-tickets)<a href="https://agentmods.dev/skills/sponge-b0b/polaris/to-remediation-tickets"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/to-remediation-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-remediation-tickets"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/to-remediation-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.00039 | $0.03058 |
| Opus 5 | $0.00019 | $0.01529 |
| Sonnet 5 | $0.00008 | $0.00612 |
| Haiku 4.5 | $0.00004 | $0.00306 |
Grade A, and why
to-remediation-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 — 436 lines — stays where its author put it; the contents beside it link to each section on GitHub.
To Remediation Tickets
Integrated Authority
This SKILL.md is the single authoritative procedure for $to-remediation-tickets.
The current hardening below supersedes only references in the preserved procedure that make $verify-root-closure a separate remediation certification authority. All other preserved procedure mechanics remain normative.
Common Closure Verifier
Every remediation ticket produced by this workflow is ultimately certified by:
$verify-ticket-closure
not by a separate $verify-root-closure algorithm.
Interpret any preserved sentence of the form:
an implementer and
$verify-root-closuremust be able to determine/prove root closure
as:
the implementer must provide complete Proposed Closure Evidence and one fresh
$verify-ticket-closureverifier must independently certify the combined ordinary + remediation acceptance universe.
The remediation delta must still carry all existing:
- Root Blocker ID and stable invariant;
- remediation obligations;
- verification-only obligations;
- same-root preservation obligations;
- production-path and negative/fail-closed proof requirements;
- root-complete invariant sweep;
- protected behavior needed for root closure.
Those obligations extend the common ticket acceptance universe. They are not weakened or converted into ordinary implementation-only claims.
One Verdict
Do not design or publish remediation tickets that require:
ordinary ticket verifier PASS
↓
root verifier PASS/FAIL
The required lifecycle is:
implementation + Proposed Closure Evidence
↓
$verify-ticket-closure
ordinary ticket obligations
+ remediation/root obligations
↓
one TICKET CLOSURE: PASS | FAIL
The historical $verify-root-closure skill exists only as a compatibility route for old handoffs and must not appear as the certification owner in newly proposed remediation tickets.
Procedure
Invoked by $to-tickets when:
- the source is a
Spec Review: ...issue; or - an existing Spec already has linked implementation tickets.
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.
- 8d ago Changed · +62 lines · -1 tokens per session a80fa1ab3712
- 12d ago First seen · 374 lines · 40 tokens per session scan A e4e1f73a39f9
to-remediation-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 3,058 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.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.