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-adr-doc/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-adr-doc)<a href="https://agentmods.dev/skills/sponge-b0b/polaris/to-adr-doc"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/to-adr-doc/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-adr-doc"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/to-adr-doc.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.00049 | $0.01805 |
| Opus 5 | $0.00024 | $0.00903 |
| Sonnet 5 | $0.00010 | $0.00361 |
| Haiku 4.5 | $0.00005 | $0.00180 |
Grade A, and why
to-adr-doc 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 — 354 lines — stays where its author put it; the contents beside it link to each section on GitHub.
To ADR Doc
$to-adr-doc is the single source of truth for ADR creation and lifecycle management.
ADRs live in:
docs/adr/
and use globally sequential numbering.
Create the directory lazily when the first ADR is needed.
ADR Format
Use the smallest structure that preserves the decision and its causal reasoning:
---
status: proposed
---
# [Short decision title]
## Context
[What problem, constraint, or architectural question requires a decision?]
## Decision
[What was decided?]
## Rationale
[Why was this option chosen over meaningful alternatives?]
Optional sections:
## Considered Options
## Consequences
Add them only when they preserve useful information.
Keep ADRs concise.
Status
Every ADR uses a status frontmatter field.
Allowed values:
proposed
accepted
rejected
deprecated
superseded by ADR-NNNN
No separate doc_class is stored; ADR classification is derived from status according to wiki/_schema.md.
Lifecycle
Allowed transitions are:
proposed → accepted
proposed → rejected
accepted → deprecated
accepted → superseded by ADR-NNNN
deprecated → superseded by ADR-NNNN
rejected and superseded are terminal.
Do not invent additional transitions.
Proposed
The decision is still being developed.
Its body may be edited while status remains proposed.
A substantive proposed-ADR edit must trigger $wiki-sync, because derived Planned knowledge may have changed even though status did not.
Accepted
The decision is active architecture.
Acceptance does not necessarily mean implementation is complete.
Once accepted, decision content becomes historical and immutable except for the narrow Realization Maintenance exception below.
Rejected
The decision was deliberately not adopted.
The body is immutable and the status is terminal.
If changed circumstances later make the direction viable, create a new ADR referencing the rejection rather than reopening it.
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 · 354 lines · 49 tokens per session scan A 38551b6a4b8b
to-adr-doc is a skill published in the GitHub repository sponge-b0b/Polaris (4 stars, last pushed today), licensed Apache-2.0. It adds 49 tokens to every session and 1,805 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
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…