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 mapping-feature-relationshipsgit 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/mapping-feature-relationships)<a href="https://agentmods.dev/skills/lerianstudio/ring/mapping-feature-relationships"><img src="https://agentmods.dev/badge/skills/lerianstudio/ring/mapping-feature-relationships/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.
<a href="https://agentmods.dev/skills/lerianstudio/ring/mapping-feature-relationships"><img src="https://agentmods.dev/badge/skills/lerianstudio/ring/mapping-feature-relationships.svg" alt="Reviewed on agentmods" width="80" 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.00104 | $0.01429 |
| Opus 5.5 | $0.00042 | $0.00572 |
| Sonnet 5.5 | $0.00021 | $0.00286 |
| Haiku 4.5 | $0.00010 | $0.00143 |
Grade A, and why
ring:mapping-feature-relationships 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 1mo 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Map Creation — Relationships and Phasing
When to use
- PRD passed Gate 1 validation
- Multiple features with complex interactions
- Need to understand feature scope, relationships, and delivery phasing
- Large Track workflow (2+ day features)
Skip when
- Small Track workflow (<2 days) → skip to TRD
- Single simple feature → TRD directly
- PRD not validated → complete Gate 1 first
Sequence
Runs before: ring:writing-trds Runs after: ring:writing-prds
Maps HOW features relate, group, and interact at a business level before architectural decisions — and defines the phasing of the work. This is the main document where the squad validates the PHASING: each phase defined here becomes, one-to-one, a phase in plan.md at Gate 7 (ring:writing-plans consumes the ## Phases section as the binding phase structure).
Mandatory Workflow
| Phase | Activities |
|---|---|
| 1. Feature Analysis | Load approved PRD (Gate 1); extract all features; identify user journeys; map feature interactions |
| 2. Feature Mapping | Categorize (Core/Supporting/Enhancement/Integration); group into domains; map user journeys; identify integration points and dependencies; define boundaries; prioritize by value |
| 3. Phasing | Slice features into delivery phases; name each phase and its milestone; assign every feature, relationship, and integration point to exactly one phase; order phases by dependency (no phase depends on a later phase) |
| 4. Gate 2 Validation | All PRD features mapped AND assigned to a phase; categories defined; domains logical; journeys complete; integration points identified; phase ordering respects dependencies; no technical details |
Categorization Rules
| Category | Criteria |
|---|---|
| Core | Must have for MVP; blocks other features |
| Supporting | Enables core features; medium priority |
| Enhancement | Improves existing; nice-to-have |
| Integration | Connects to external systems |
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.
- 1mo ago First seen · 153 lines · 104 tokens per session scan A b3cf175e9174
ring:mapping-feature-relationships is a skill published in the GitHub repository LerianStudio/ring (218 stars, last pushed 7d ago), licensed Apache-2.0. It adds 104 tokens to every session and 1,429 once invoked, about $0.0004 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-03.
Other skills, from other repositories
backlog
Manage the project's tech debt backlog. Add, list, fix, wontfix, delete, prioritize, and suggest batch actions on tracked issues, run by the user to manage accumulated debt (skills file their findings through /.zuvo/backlog-add themselves, never through this skill). Modes: list [category], add [description], fix B- …
retro
Engineering retrospective from git metrics. Reports deployment frequency, release cycle span, churn hotspots, backlog health. Outputs narrative report with 3+ actionable items. Flags: --since, --path, explicit range argument.
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
publish-artifacts-to-r3
Publish HTML pages, documents, files, or code changes to r3 for human review, and respond to feedback on existing r3 artifacts. Use when the user asks to use r3 or supplies an r3 artifact or feedback command.
revert
Git-aware revert that understands Draft tracks, phases, and tasks. Safely undo work at task, phase, or track level. Use when the user asks to 'revert this track', 'undo a phase', 'revert task X', or says 'roll back the last task', 'undo this work'.