A workflow for creating a new non-ADR document under a project's docs folder. An ADR is an Architecture Decision Record, a document that records an important technical decision.

Classifying new documents as current, proposed, research, reference, or process, choosing their names and locations, and synchronizing the wiki when needed.

It prevents new documents from being placed, named, or classified inconsistently. It also checks whether another workflow owns the requested location or whether the document should be an ADR.

How sponge-b0b/Polaris configures Claude Code and Codex

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/sponge-b0b/Polaris/main/.agents/skills/to-doc/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/sponge-b0b/Polaris

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/sponge-b0b/polaris/to-doc/github.svg)](https://agentmods.dev/skills/sponge-b0b/polaris/to-doc)

Your own site

<a href="https://agentmods.dev/skills/sponge-b0b/polaris/to-doc"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/to-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/sponge-b0b/polaris/to-doc"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/to-doc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,156 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00034	$0.01156
Opus 5	$0.00017	$0.00578
Sonnet 5	$0.00007	$0.00231
Haiku 4.5	$0.00003	$0.00116

Measured 5d ago against content hash 7e5ccd1c9775, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

to-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 5d 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.

.agents/skills/to-doc/SKILL.md · 179 lines

How it starts

The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.

To Doc

$to-doc owns creation-time placement and naming of new Living Entity Wiki-classified non-ADR documents under docs/.

Its responsibility is:

content
  ↓
classify
  ↓
name
  ↓
write
  ↓
sync when required

Classification, naming, and the docs/.wikiignore exclusion boundary are owned by wiki/_schema.md.

For an existing classified document, use $classify-doc.

For an ADR, use $to-adr-doc.

1. Confirm Scope

Use this skill only for a new non-ADR document inside the Living Entity Wiki document universe.

If the content warrants an ADR, use $to-adr-doc.
If the document already exists, use $classify-doc.
If the requested path is matched by docs/.wikiignore, it is outside this skill's ownership; use the workflow or repository owner responsible for that documentation tree.
Do not recreate an existing document merely to bypass reclassification or reference migration.

2. Classify the Document

Apply the non-ADR classification rules in wiki/_schema.md.

Possible project-owned classes are:

current
proposed
research
reference
process

Classification comes from folder placement.

Do not add:

doc_class:
Doc-Class:

to the document.

If current vs proposed is genuinely unclear, follow the schema fail-safe and use proposed.

3. Respect the Wiki Exclusion Boundary

Read docs/.wikiignore when present and apply only the exclusion grammar defined by wiki/_schema.md.

If the requested path is explicitly excluded:

do not classify it;
do not apply Living Entity Wiki naming rules;
do not invoke $wiki-sync solely because it was created;
route creation to the workflow or repository owner responsible for that documentation tree.

Do not infer exclusions for unfamiliar directories and do not invent new .wikiignore entries merely to make a requested path legal.

4. Name the Document

Apply the naming and cross-cutting-document rules in wiki/_schema.md.

When an active wiki/index.md exists:

Read the full file on GitHub · 179 lines

Changes

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.

5d ago Changed · +7 lines · +3 tokens per session 7e5ccd1c9775
9d ago First seen · 172 lines · 31 tokens per session scan A c23b97a52a6e

Subscribe to this mod's changes

to-doc is a skill published in the GitHub repository sponge-b0b/Polaris (4 stars, last pushed today), licensed Apache-2.0. It adds 34 tokens to every session and 1,156 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.

Writing and docs

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens

Polaris: Skill for Claude Code