agentmods.dev

rings

rings is a skill for Claude Code from digital-stoic-org/agent-skills. It costs 52 tokens per session (1,043 once invoked), scanned A, original, MIT.

A read-only skill for inspecting a ring directory, including its work tree, file-ownership claims, collisions, and anomalies. Mermaid is a diagram format used here to show the ring relationships visually.

In plain words
What is it for?
Use it to list open rings, view their hierarchy, inspect claims, and find possible ownership conflicts.
Why use it?
It lets you check the state of nested work without changing files. It can reveal missing links between parent and child rings and overlapping path claims.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the ring plugin — 4 skills shipped together

not rated 20repo changed 5d ago A scan 52 tokens original MIT

Good fit Use it to list open rings, view their hierarchy, inspect claims, and find possible ownership conflicts.

Compare 6 skills from other repositories ↓
View source ↗ digital-stoic-org/agent-skills
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add digital-stoic-org/agent-skills
Claude Code
/plugin install ring

Made for: Claude Code.

Or install ring, the plugin that ships this one along with the rest of its 4 skills.

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 rings

README.md
[![agentmods](https://agentmods.dev/badge/skills/digital-stoic-org/agent-skills/rings/github.svg)](https://agentmods.dev/skills/digital-stoic-org/agent-skills/rings)
Your own site
<a href="https://agentmods.dev/skills/digital-stoic-org/agent-skills/rings"><img src="https://agentmods.dev/badge/skills/digital-stoic-org/agent-skills/rings/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 rings

Your own site · 80×15
<a href="https://agentmods.dev/skills/digital-stoic-org/agent-skills/rings"><img src="https://agentmods.dev/badge/skills/digital-stoic-org/agent-skills/rings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,043 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.00052 $0.01043
Opus 5.5 $0.00021 $0.00417
Sonnet 5.5 $0.00010 $0.00209
Haiku 4.5 $0.00005 $0.00104

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

Security

Grade A, and why

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

ring/skills/rings/SKILL.md · 48 lines

How it starts

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

Rings

Read-only. Writes nothing, ever.

Arguments

Argument Value Default
[dir] absolute path to the ring directory the ring directory known from context; if unknown, ask
--claims print only the claims table + collisions, skip the tree off
--verbose full claims table (every claim, not only collisions), exact ring.py commands run off

Steps

  1. python3 ${CLAUDE_PLUGIN_ROOT}/scripts/ring.py scan <dir> — covers <dir> root and <dir>/done/. Exit 1 only means some ring carries an anomaly; keep going, anomalies are surfaced, not fatal. Read each ring's anomalies[]. If scan returns [], this does not mean the folder is virgin — see the blind-spot sentence under Output; still run steps 2-4, the footer's measured: line covers all three commands regardless.
  2. Skip if --claims. python3 ${CLAUDE_PLUGIN_ROOT}/scripts/ring.py graph <dir> — a Mermaid flowchart TD. Node label = slug<br/>(vehicle · carrier) when the ring's carrier field is non-null, slug<br/>(vehicle) when it is absent or — (v0.1.0 files, or nobody holds the token). Color: active green, parked gold, done gray, root blue. A children: slug with no matching file, or a parent: with no matching file, renders as a dashed phantom node — this is expected for inline/subagent rings, which have no file. done rings stay on the tree, never pruned.
  3. python3 ${CLAUDE_PLUGIN_ROOT}/scripts/ring.py collide <dir> — every create:/writes: claim of every active/parked ring (root + done/), paired up where one includes the other. relation: lineage is a legal parent→child delegation (§4.2), not a problem. Only relation: none pairs are real collisions.
  4. Compose the anomaly list from step 1's anomalies[] fields plus step 3's none-relation pairs. List them flat. Never fix them — this skill only reads.

Output

Default (natural language, not a field dump):

  • The Mermaid tree (omitted under --claims).
  • One sentence of counts, natural language: e.g. "3 rings active, 1 closed, no anomaly."
  • The claims table — only when step 3 found a none-relation collision, or --claims was passed. Otherwise omitted; nothing to look at.
  • Each parked ring flagged as resumable: <slug> (parked) — resume with /open --resume <slug>.
  • Blind-spot sentence, only when scan returned []: this view only covers rings that have a file; inline rings not yet promoted and subagent rings are invisible by construction — an empty result is not proof the folder is unused. Point at /ring:sync to promote an inline ring into view.
  • Footer: measured: scan+graph+collide on <dir> · <ts>.

Read the full file on GitHub · 48 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. 5d ago Changed · +7 lines ea1b4f6b86b3
  2. 6d ago First seen · 41 lines · 52 tokens per session scan A 0338ccf9eca1

Subscribe to this mod's changes

rings is a skill published in the GitHub repository digital-stoic-org/agent-skills (20 stars, last pushed 2d ago), licensed MIT. It adds 52 tokens to every session and 1,043 once invoked, about $0.0002 per session on Opus 5.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-09-24.

Building agents
Related

Other skills, from other repositories

systematic-debugging

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

obra/superpowers · 21 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

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 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

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