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-specs/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-specs)<a href="https://agentmods.dev/skills/sponge-b0b/polaris/to-remediation-specs"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/to-remediation-specs/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-specs"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/to-remediation-specs.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.00054 | $0.02162 |
| Opus 5 | $0.00027 | $0.01081 |
| Sonnet 5 | $0.00011 | $0.00432 |
| Haiku 4.5 | $0.00005 | $0.00216 |
Grade A, and why
to-remediation-specs 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 11d 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.
To Remediation Specs
Invoked by $to-specs when its source Wayfinder map already has one or more in-progress Spec handoffs.
Replace fresh spec creation for that handed-off scope. The Wayfinder map remains the source input for the current remediation decisions.
Session Independence
Assume no prior conversational or agent-session state.
Recover every correctness-critical input from the explicit invocation, repository, and durable tracker artifacts before acting. Prior-session summaries or remembered conclusions are routing context only and must not substitute for required durable evidence.
If required durable state cannot be recovered, report the missing artifact rather than infer or recreate it from memory.
1. Recover the Existing Specs
From the source Wayfinder map, resolve every in-progress Spec identified by the reconciled Derived Spec and Remediation Spec metadata established by $to-specs.
For a Derived Spec, confirm its durable source provenance identifies the input Wayfinder.
For a Remediation Spec, preserve its original source provenance even when it identifies another Wayfinder. Confirm instead that the input Wayfinder explicitly names the Spec as a Remediation Spec or that the Spec already has a wayfinder-remediation marker for the input Wayfinder.
If tracker evidence reveals an additional unambiguous handed-off Spec missing from the map's Spec Handoff, add the matching linkage and include that Spec before continuing.
Preserve each Spec's:
- issue identity;
- original planning/source provenance;
- branch and baseline lineage;
- existing tickets;
- Spec Review lineage, when present.
If no in-progress handed-off Specs exist, return to $to-specs for normal spec creation.
If any candidate relationship or handoff role is ambiguous, halt rather than guessing which Specs belong to the current remediation run.
2. Recover Decision Provenance
For each Derived Spec, read its source Wayfinder provenance marker:
<!-- wayfinder-source: #<map>; decisions: #<decision>,#<decision> -->
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.
- 11d ago First seen · 248 lines · 54 tokens per session scan A 6bddbc16b43e
to-remediation-specs is a skill published in the GitHub repository sponge-b0b/Polaris (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 54 tokens to every session and 2,162 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…