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 pinning-dependency-versionsgit 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/pinning-dependency-versions)<a href="https://agentmods.dev/skills/lerianstudio/ring/pinning-dependency-versions"><img src="https://agentmods.dev/badge/skills/lerianstudio/ring/pinning-dependency-versions.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.00102 | $0.01396 |
| Opus 5 | $0.00051 | $0.00698 |
| Sonnet 5 | $0.00020 | $0.00279 |
| Haiku 4.5 | $0.00010 | $0.00140 |
Grade A, and why
ring:pinning-dependency-versions 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Map — Explicit Technology Choices
When to use
- Schema (schema.sql / schema.prisma) passed Gate 5 validation
- About to select specific technologies
- Large Track workflow (2+ day features)
Skip when
- Small Track workflow → skip to ring:writing-plans
- Technologies already locked → skip to ring:writing-plans
- Schema not validated → complete Gate 5 first
Sequence
Runs before: ring:writing-plans Runs after: ring:designing-data-model
Every technology choice must be explicit, versioned, validated against Ring Standards, and justified. The Dependency Map answers WHAT specific products, versions, packages, and infrastructure will be used.
Step 0: Standards Loading (HARD GATE)
Step 0.1: Read Technology Decisions from TRD
Read docs/pre-dev/{feature}/trd.md — extract: deployment.model, tech_stack.primary, project_technologies[].
If TRD metadata missing → STOP: "Go back to TRD (Gate 3) and complete Step 0.4."
Step 0.2: Load Ring Standards via WebFetch
| Standard | URL |
|---|---|
| golang/index.md | https://raw.githubusercontent.com/LerianStudio/ring/main/dev-team/docs/standards/golang/index.md |
| typescript.md | https://raw.githubusercontent.com/LerianStudio/ring/main/dev-team/docs/standards/typescript.md |
| frontend.md | https://raw.githubusercontent.com/LerianStudio/ring/main/dev-team/docs/standards/frontend.md |
| devops.md | https://raw.githubusercontent.com/LerianStudio/ring/main/dev-team/docs/standards/devops.md |
| sre.md | https://raw.githubusercontent.com/LerianStudio/ring/main/dev-team/docs/standards/sre.md |
Step 0.3: Generate PROJECT_RULES.md (OUTPUT)
Using TRD project_technologies[], create docs/PROJECT_RULES.md with: deployment model, tech stack, per-category decisions (PRD requirement, technology, version, rationale, cloud service, on-premise alternative), version matrix, security/compliance notes.
Mandatory Workflow
| Phase | Activities |
|---|---|
| 1. Evaluation | Ring Standards loaded; map TRD components to tech candidates; validate against Ring Standards; map the schema file (schema.sql / schema.prisma) to storage; map openapi.yaml contracts to protocols; check team expertise; estimate costs |
| 2. Selection | Per technology: check Ring Standards (mandatory/prohibited), specify exact version, list alternatives with trade-offs, verify compatibility, check security (CVEs), validate licenses, calculate costs |
| 3. Gate 6 Validation | All dependencies explicit; no conflicts; no critical CVEs; licenses compliant; costs documented; all components mapped |
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 · 127 lines · 102 tokens per session scan A eed3e6f6c131
ring:pinning-dependency-versions is a skill published in the GitHub repository LerianStudio/ring (211 stars, last pushed 19d ago), licensed Apache-2.0. It adds 102 tokens to every session and 1,396 once invoked, about $0.0005 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.