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/analyzing-optionsnpx skills add LerianStudio/ring --skill analyzing-optionsgit 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/analyzing-options)<a href="https://agentmods.dev/skills/lerianstudio/ring/analyzing-options"><img src="https://agentmods.dev/badge/skills/lerianstudio/ring/analyzing-options.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00054 | $0.00650 |
| Opus 5 | $0.00027 | $0.00325 |
| Sonnet 5 | $0.00011 | $0.00130 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
ring:analyzing-options 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 4d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyzing Options
When to use
- Facing multiple viable approaches to a task or problem
- Making strategic decisions or architecture choices
- Needing structured comparison with effort estimates
- Evaluating trade-offs between competing solutions
Skip when
- There's an obvious single approach
- The decision is already made
- The task is trivial and doesn't warrant analysis
Related
Similar: ring:writing-plans — use writing-plans when the approach is decided and you need phased execution
For the given task or problem, provide a structured analysis following this format:
Instructions
1. Problem Understanding
- Clearly restate the problem/goal
- Identify key requirements and constraints
- List any assumptions being made
2. Approach Options
For each viable approach (aim for 3-5 options):
Option [N]: [Descriptive Name]
Overview: Brief description of the approach
Benefits:
- List 3-5 key advantages
- Focus on technical and business value
Trade-offs:
- List 2-4 potential drawbacks or limitations
- Be honest about complexity or risks
Implementation Details:
- High-level steps required
- Key technologies or patterns involved
- Integration points or dependencies
Effort Estimate:
- Complexity: Low/Medium/High
- Time: Rough estimate (hours/days/weeks)
- Team Size: Solo developer / Small team / Large team
- Maintenance: Ongoing effort required
Best For: Describe scenarios where this approach excels
3. Recommendation Matrix
Create a comparison table:
| Approach | Complexity | Time | Risk | Scalability | Maintainability | Overall Score |
|---|---|---|---|---|---|---|
| Option 1 | Low | 2d | Low | Medium | High | 7/10 |
| Option 2 | High | 2w | Med | High | Medium | 6/10 |
| etc... |
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.
- 4d ago First seen · 98 lines · 54 tokens per session scan A c6ec91a0563f
ring:analyzing-options is a skill published in the GitHub repository LerianStudio/ring (210 stars, last pushed 15d ago), licensed Apache-2.0. It adds 54 tokens to every session and 650 once invoked, about $0.0003 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.
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.
incident
Incident response and postmortem generation from git/deploy context. When something breaks in production, this skill builds a timeline, identifies the probable cause, and generates a structured postmortem document. Flags: --since, --service, --sev, --revert, --comms, --dry-run.
performance-audit
Full-stack performance health check across 12 dimensions. Rendering, bundles, assets, API/network, algorithms, memory, database, caching, Web Vitals, backend runtime, concurrency, and framework-specific pathologies. Evidence-based Impact Models with confidence tiers and a prioritized optimization roadmap. Switches…