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-tw-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-tw-team)<a href="https://agentmods.dev/skills/lerianstudio/ring/using-tw-team"><img src="https://agentmods.dev/badge/skills/lerianstudio/ring/using-tw-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.00080 | $0.00994 |
| Opus 5 | $0.00040 | $0.00497 |
| Sonnet 5 | $0.00016 | $0.00199 |
| Haiku 4.5 | $0.00008 | $0.00099 |
Grade A, and why
ring:using-tw-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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Ring Technical Writing Specialists
When to use
- Need to write functional documentation (guides, conceptual docs, tutorials)
- Need to write API reference documentation
- Need to review existing documentation quality
- Writing or updating product documentation
Skip when
- Writing code → use dev-team agents
- Writing plans → use pm-team agents
- General code review → use
ring:reviewing-codewith dev-team reviewer agents
Related
Similar: ring:using-ring, ring:using-dev-team
The ring-tw-team plugin provides specialized agents for technical documentation. Use them via Task tool with subagent_type:.
Remember: Follow the ORCHESTRATOR principle from ring:using-ring. Dispatch agents to handle documentation tasks; don't write complex documentation directly.
3 Documentation Specialists
| Agent | Specialization | Use When |
|---|---|---|
ring:guide-writer |
Conceptual docs, guides, tutorials, best practices, workflows | Writing product guides, tutorials, "how to" content |
ring:api-writer |
REST API reference, endpoints, schemas, errors, field descriptions | Documenting API endpoints, request/response examples |
ring:docs-reviewer |
Voice/tone, structure, completeness, clarity, accuracy | Reviewing drafts, pre-publication quality check |
Documentation Standards Summary
Voice and Tone
- Assertive, but never arrogant – Say what needs to be said, clearly
- Encouraging and empowering – Guide users through complexity
- Tech-savvy, but human – Use technical terms when needed, prioritize clarity
- Humble and open – Confident but always learning
Capitalization
- Sentence case for all headings and titles
- Only first letter and proper nouns capitalized
- ✅ "Getting started with the API"
- ❌ "Getting Started With The API"
Structure Patterns
- Lead with clear definition paragraph
- Use bullet points for key characteristics
- Separate sections with
---dividers - Include info boxes and warnings where needed
- Link to related API reference
- Add code examples for technical topics
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 · 119 lines · 80 tokens per session scan A 123fdeabd172
ring:using-tw-team is a skill published in the GitHub repository LerianStudio/ring (211 stars, last pushed 19d ago), licensed Apache-2.0. It adds 80 tokens to every session and 994 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.