poly-tiers-and-scope

poly-tiers-and-scope is a skill for Claude Code from Goldziher/poly. It costs 61 tokens per session (2,030 once invoked), scanned A, original, MIT.

A guide to how poly chooses the checks and formatters applied to each file. It explains built-in language tools, general syntax-based checks, native language command-line tools, and files that are excluded or specially handled.

In plain words
What is it for?
Use it to understand poly's language coverage, configure tool selection, investigate scope problems, and choose appropriate checks for less common languages.
Why use it?
It helps explain why a particular file was or was not checked, and what level of formatting support to expect for each language.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the poly plugin — 5 skills, 2 commands, 2 agents shipped together

Good fit Use it to understand poly's language coverage, configure tool selection, investigate scope problems, and choose appropriate checks for less common languages.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/goldziher/poly/poly-tiers-and-scope
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Goldziher/poly --skill poly-tiers-and-scope
Clone the repo
git clone --depth 1 https://github.com/Goldziher/poly

Made for: Claude Code.

Or install poly, the plugin that ships this one along with the rest of its 5 skills, 2 commands, 2 agents.

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.

agentmods badge for poly-tiers-and-scope

README.md
[![agentmods](https://agentmods.dev/badge/skills/goldziher/poly/poly-tiers-and-scope/github.svg)](https://agentmods.dev/skills/goldziher/poly/poly-tiers-and-scope)
Your own site
<a href="https://agentmods.dev/skills/goldziher/poly/poly-tiers-and-scope"><img src="https://agentmods.dev/badge/skills/goldziher/poly/poly-tiers-and-scope/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.

agentmods 80×15 button for poly-tiers-and-scope

Your own site · 80×15
<a href="https://agentmods.dev/skills/goldziher/poly/poly-tiers-and-scope"><img src="https://agentmods.dev/badge/skills/goldziher/poly/poly-tiers-and-scope.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,030 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00061 $0.02030
Opus 5 $0.00030 $0.01015
Sonnet 5 $0.00012 $0.00406
Haiku 4.5 $0.00006 $0.00203

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

Security

Grade A, and why

poly-tiers-and-scope 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 4d 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.

.ai-rulez/skills/poly-tiers-and-scope/SKILL.md · 119 lines

How it starts

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

poly Tiers and Scope

Coverage tiers inside the per-file pass

Five mechanisms decide what actually inspects a file (crates/poly-core/src/registry.rs):

  1. Tier-1 native crate backends — one in-process Rust crate registered for specific languages: ruff, oxc, taplo, rumdl, sqruff, yaml, malva (+ biome for CSS/SCSS), markup_fmt, mago, rubyfmt, graphql, nixfmt, hcl, dockerfile, dotenv, ini.
  2. Tier-2 tree-sitter generic tier (ADR 0004) — the catch-all for every language with no native backend. Structural reindent for brace-family grammars, whitespace normalization otherwise, and a leave-untouched list where whitespace is significant. This is the coverage mechanism, not a fallback to avoid — but it is explicitly not gofmt/rustfmt parity.
  3. Native-toolchain tier (ADR 0014, engines/native_tool/) — the language's canonical first-party CLI, run per file over stdin/stdout. rustfmt, gofmt and shellcheck are on by default whenever the tool is found on PATH; zig fmt, shfmt, google-java-format, ktfmt, styler, swift-format, dart format, and gleam format are opt-in via [fmt.<lang>.<tool>] enabled = true / [lint.<lang>.<tool>] enabled = true. Absent tool ⇒ the language falls through to tier 2 with an info-level notice, never an error.
  4. quality, the code-quality metric tier (ADR 0027) — cross-cutting, appended to every language: file/function/type length, nesting depth, cyclomatic complexity, parameter count, and lazy-ignore. Warning severity, on by default, configured under [lint.quality]. The structural rules need a verified node-kind table and cover Python, Rust, Go, JavaScript, TypeScript, TSX, Java, Kotlin, C, C++, C#, and Ruby; magic-number and law-of-demeter are opt-in. A per-language deferral table keeps it from duplicating a tier-1 rule (ruff's C901/PLR0913, oxlint's max-depth/max-params).
  5. The built-in ast-grep rule pack (ADR 0029) — 26 rules across 9 languages (C#, Elixir, Go, Java, Kotlin, Python, Ruby, Rust, Swift) embedded in the binary and on by default; 13 of them ship severity: off. It sits beneath [rules] dirs (default .poly/rules), so a user rule with the same id replaces a pack rule. [rules] builtin = false disables the pack wholesale.

Read the full file on GitHub · 119 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.

  1. 4d ago Changed · +15 lines a30db3e06584
  2. 9d ago First seen · 104 lines · 61 tokens per session scan A 2106f4ce46dd

Subscribe to this mod's changes

poly-tiers-and-scope is a skill published in the GitHub repository Goldziher/poly (16 stars, last pushed 8d ago), licensed MIT. It adds 61 tokens to every session and 2,030 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.

Related

Other skills, from other repositories

argot-refresh

Refresh Argot's committed fit snapshot safely — first diagnose why maintenance is recommended, re-audit corpus scope and structural path changes, review stale mutes and policy entries with the user, then fit locally, verify, and prepare the reviewed .argot/ update. Use when argot status, argot check, MCP, or CI…

get-tmonier/argot · 136 tokens

ph-debug

(PH) Use for a reproducible failure or unexpected behavior; reproduce, isolate, and verify the cause.

jyt6640/persona-harness · 25 tokens

ph-lsp-setup

(PH) Use only when the user explicitly requests language-server setup or diagnostics.

jyt6640/persona-harness · 22 tokens

printing-press-amend

Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts user-supplied asks (rename a command, add commands or feeds, fix a named bug, optionally…

mvanhorn/cli-printing-press · 222 tokens

printing-press-output-review

Internal sub-skill: agentic review of a printed CLI's sampled command output for plausibility issues that rule-based checks can't encode (substring-match relevance, format bugs, silent source drops, ranking failures). Invoked via the Skill tool by the main printing-press skill at Phase 4.85 and printing-press-polish…

mvanhorn/cli-printing-press · 102 tokens

fix

Dispatch fix subagent for FIX-FIRST gaps from review, re-review, then diagnose unresolved failures after 2 loops.

automagik-dev/genie · 25 tokens