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.
npx agentmods add skills/lerianstudio/ring/using-ringnpx skills add LerianStudio/ring --skill using-ringgit clone --depth 1 https://github.com/LerianStudio/ringWhat 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 | $0.00084 | $0.00868 |
| Opus 5 | $0.00042 | $0.00434 |
| Sonnet 5 | $0.00017 | $0.00174 |
| Haiku 4.5 | $0.00008 | $0.00087 |
Grade A, and why
ring:using-ring 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 2d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Ring (Orchestrator Protocol)
When to use
- Every conversation start (automatic via SessionStart hook)
- Before ANY task (check for applicable skills)
- When tempted to operate tools directly instead of delegating
Skip when
- Never skip - this skill is always mandatory
⛔ 3-FILE RULE: HARD GATE
DO NOT read/edit >3 files directly. PROHIBITION, not guidance.
≤3 files → Direct OK (if user requested)
>3 files → STOP. Launch agent. VIOLATION = 15x context waste.
Already at 3 files? STOP. Dispatch agent NOW.
Auto-Trigger Phrases: Mandatory Agent Dispatch
| User Phrase | Mandatory Action |
|---|---|
| "fix issues", "fix remaining", "fix findings" | Launch specialist agent |
| "apply fixes", "fix errors", "fix warnings", "fix linting" | Launch specialist agent |
| "update across", "change all", "refactor" | Launch specialist agent |
| "find where", "search for", "understand how" | Launch Explore agent |
| "draw diagram", "visualize", "comparison table" | Load ring:visualizing skill |
Mandatory First Response Protocol
- ☐ Check for
<MANDATORY-USER-MESSAGE>in additionalContext — display verbatim if present - ☐ Orchestration decision: which agent handles this? (TodoWrite)
- ☐ Skill check: does any skill match this request?
- ☐ If yes → read and run the skill
- ☐ Announce skill/agent being used
- ☐ Execute
ORCHESTRATOR Principle
You dispatch agents. You do not operate tools directly.
| Instead of... | Do this |
|---|---|
| Reading files | Dispatch Explore agent |
| Grep/Glob chains | Dispatch Explore agent |
| Manual multi-file edits | Dispatch specialist agent |
| "Quick look" at codebase | Dispatch Explore agent |
Exceptions (rare): User explicitly provides a file path AND explicitly requests you read it.
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.
- 2d ago First seen · 97 lines · 84 tokens per session scan A 38fc0ea9c04f
ring:using-ring is a skill published in the GitHub repository LerianStudio/ring (210 stars, last pushed 13d ago), licensed Apache-2.0. It adds 84 tokens to every session and 868 once invoked, about $0.0004 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-30.
Other skills, from other repositories
brainstorm
Explores a codebase, researches the problem space, and produces an approved design specification before any code is written. Use when the user wants to create a new feature, add significant functionality, redesign a subsystem, or build something that touches multiple parts of the project.
pentest
Hybrid white-box + black-box penetration testing across 7 dimensions (PT1-PT7). Stack-aware source-to-sink tracing, exploit verification, CMS overlay, and deterministic finding aggregation. Uses explicit candidate schemas, canonical-key deduplication, score caps, and MUST-GATE enforcement. Flags: zuvo:pentest [path] |…
debt-ops-init
Write or refresh a "Tech debt operations" section in the project's AGENTS.md so the team shares one source of truth for debt-ops disciplines. Run ONLY when the user explicitly asks to set up, install, or initialize debt-ops disciplines — never auto-invoke. Idempotent; only the managed section changes, other sections…
a11y-audit
Dedicated WCAG 2.2 AA/AAA accessibility audit across 10 dimensions (A1-A10) covering semantic HTML, keyboard navigation, ARIA patterns, color contrast, forms, images/media, responsive/zoom, motion/animation, reading/content, and legal compliance. Goes far beyond surface-level design-review checks with deep…
api-audit
API and endpoint integrity audit across 10 dimensions (D1-D10) plus optional contract stability (D11) and optional OWASP API Security Top 10 (D12: BOLA/BOPLA/BFLA, mass assignment, JWT alg-confusion, GraphQL introspection). Covers validation, payloads, pagination, errors, caching, HTTP semantics, waterfalls, rate…
debug
Systematic bug investigation with a five-phase framework: reproduce, narrow, diagnose, fix, verify. Supports automated regression bisect via --regression flag. Produces a structured debug report with root cause analysis, regression test, and CQ/Q self-evaluations.