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 skills add LerianStudio/ring --skill using-dev-teamgit clone --depth 1 https://github.com/LerianStudio/ringWrote 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/lerianstudio/ring/using-dev-team)<a href="https://agentmods.dev/skills/lerianstudio/ring/using-dev-team"><img src="https://agentmods.dev/badge/skills/lerianstudio/ring/using-dev-team.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00082 | $0.01082 |
| Opus 5 | $0.00041 | $0.00541 |
| Sonnet 5 | $0.00016 | $0.00216 |
| Haiku 4.5 | $0.00008 | $0.00108 |
Grade A, and why
ring:using-dev-team 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Ring Developer Specialists
When to use
- Need deep expertise for specific technology (Go, TypeScript)
- Backend local runtime / docker-compose → ring:backend-go or ring:backend-ts
- Frontend with design focus → ring:ui-designer
- Frontend UI development (React/Next.js) → ring:frontend
- Frontend from product-designer specs → ring:ui-engineer
- Helm chart creation/maintenance → ring:helm
- Backend tests / coverage / TDD → ring:backend-go or ring:backend-ts
- Frontend test strategy → ring:qa-frontend
- Backend health/logging/tracing → ring:backend-go or ring:backend-ts
- Agent/prompt quality evaluation → ring:prompt-reviewer
- Migrating deprecated lib-commons observability shims to lib-observability → ring:migrating-to-lib-observability
Skip when
- General code review → use
ring:reviewing-codewith dev-team reviewer agents - Debugging → trace from logs / metrics / telemetry
Related
Similar: ring:using-ring
Developer specialist agents. Dispatch via Task tool with subagent_type:.
Runtime Version Resolution
Always resolve lib-commons to latest v5.x at runtime:
gh api repos/LerianStudio/lib-commons/releases/latest --jq '.tag_name'
Do NOT hardcode specific patch versions.
Specialists
| Agent | Specializations | Use When |
|---|---|---|
ring:backend-go |
Go microservices, PostgreSQL/MongoDB, RabbitMQ, OAuth2/JWT, gRPC, concurrency | Go services, DB optimization, auth/authz, concurrency |
ring:backend-ts |
TypeScript/Node.js, Express/Fastify/NestJS, Prisma/TypeORM, Jest/Vitest | TS backends, NestJS design, JS→TS migration |
ring:bff-ts |
Next.js BFF, Clean/Hexagonal Architecture, DDD patterns, Inversify DI | BFF layer, Clean Architecture, DDD domains, API orchestration |
ring:ui-designer |
Bold typography, color systems, animations, unexpected layouts | Landing pages, portfolios, design systems |
ring:frontend |
React/Next.js, App Router, Server Components, accessibility, performance | Financial dashboards, enterprise apps, modern React |
ring:helm |
Helm charts, Lerian conventions, chart structure, security, operational patterns | Creating/maintaining Helm charts, platform deployments |
ring:ui-engineer |
Wireframe-to-code, Design System compliance, UI states implementation | Implementing from product-designer specs |
ring:prompt-reviewer |
Agent quality analysis, prompt deficiency detection, quality scoring | Evaluating agent executions, identifying prompt gaps |
ring:qa-frontend |
Vitest, Testing Library, axe-core, Playwright, Lighthouse, snapshot testing | Frontend test planning, accessibility, E2E, performance |
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 First seen · 104 lines · 82 tokens per session scan A 8664e01b3fc0
ring:using-dev-team is a skill published in the GitHub repository LerianStudio/ring (211 stars, last pushed 19d ago), licensed Apache-2.0. It adds 82 tokens to every session and 1,082 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-09-03.
Other skills, from other repositories
calibration
Internal dynos-work skill. Agent calibration — generates project-specific agents, benchmarks them, promotes/demotes based on performance, and manages auditor mode transitions. Runs only when the user explicitly types /dynos-work:calibration; never auto-triggered from conversation.
maintain
Internal dynos-work skill. Autonomous maintenance worker. Scans the repo for technical debt, security anti-patterns, and architectural drift; on a finding it creates a repair branch, implements the fix, verifies with audits/tests, and opens a Pull Request. Runs only when the user explicitly types /dynos-work:maintain…
ds-brief
Data-backed brief — research, source, double-verify, and render a visually rich single-file HTML report. Use when the user wants a sourced, fact-checked brief or report on a topic.
ds-ship
Ship orchestrator — classify the project, pick a mode (improve/release/launch/maintain), delegate only the skills the project's signals justify, consolidate findings, produce an audit report. Use for an end-to-end audit or ship pipeline across multiple skills.
trajectory
Internal dynos-work skill. Sequence memory manager. Stores compact task traces and retrieves similar prior tasks to inform discovery and design review. Runs only when the user explicitly types /dynos-work:trajectory; never auto-triggered from conversation.
ds-deploy
Deployment and infrastructure — containerization, deployment, monitoring, incident response. Use when deploying an app, setting up containers/monitoring, or planning incident response.