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/using-assertnpx skills add LerianStudio/ring --skill using-assertgit 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-assert)<a href="https://agentmods.dev/skills/lerianstudio/ring/using-assert"><img src="https://agentmods.dev/badge/skills/lerianstudio/ring/using-assert.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.1 | $0.00099 | $0.01974 |
| Opus 5 | $0.00049 | $0.00987 |
| Sonnet 5 | $0.00020 | $0.00395 |
| Haiku 4.5 | $0.00010 | $0.00197 |
Grade A, and why
ring:using-assert 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 3d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ring:using-assert
Moved from lib-commons
The canonical home for this package is now github.com/LerianStudio/lib-observability/assert. It lived in github.com/LerianStudio/lib-commons/v4/commons/assert and github.com/LerianStudio/lib-commons/v5/commons/assert through the v4 and v5 shim period; lib-commons v5 still re-exports every symbol via type aliases and thin wrappers for backward compatibility, but every type and function in lib-commons/v5/commons/assert is marked Deprecated: and delegates to lib-observability/assert. New code MUST import github.com/LerianStudio/lib-observability/assert. Existing imports continue to compile during the deprecation window — there are no behavior changes, only an import-path move.
When to use
Sweep mode:
- "Sweep the codebase for lib-observability/assert opportunities"
- "Audit this service for zero-panic policy compliance"
- "Find panic()/log.Fatal violations"
- "Replace DIY invariant checks with lib-observability/assert"
Reference mode:
- "What's the signature for assert.DebitsEqualCredits?"
- "How do I initialize assertion metrics?"
- "Should I panic, assert, or return an error here?"
- "How do I unwrap AssertionError in a Fiber error handler?"
Skip when
- Working on non-Go services
- Working on frontend code
- Target codebase is Ring itself
Related
Similar: ring:using-lib-observability, ring:using-runtime Compatibility: ring:using-lib-commons (covers the v5 deprecation shim and re-export aliases)
Mode Selection
| Request Shape | Mode |
|---|---|
| "Sweep / audit for assert opportunities" | Sweep |
| "Find panic()/log.Fatal() violations" | Sweep |
| "What's the signature for X?" | Reference |
| "Should I panic, assert, or return error?" | Reference |
SWEEP MODE
4-phase sweep. Each phase has a hard gate — do not proceed until the current phase produces its artifact.
Phase 1: Version Reconnaissance → assert-version-report.json
Phase 2: CHANGELOG Delta Analysis → assert-delta-report.json
Phase 3: Multi-Angle DIY Sweep → 6 × assert-sweep-{N}-{angle}.json
Phase 4: Consolidated Report → assert-sweep-report.md + assert-sweep-tasks.json
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 166 lines · 99 tokens per session scan A 97cb6be42faa
ring:using-assert is a skill published in the GitHub repository LerianStudio/ring (211 stars, last pushed 17d ago), licensed Apache-2.0. It adds 99 tokens to every session and 1,974 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
ops
Use this agent when you need to generate operational tooling for a project - admin/monitoring panels, debug mode overlays, or end-user feedback forms.
bug-fix
Guided end-to-end bug-fix workflow for Plan Forge tempering bugs — load → pre-fix review → write failing test → fix → validate → post-fix sweep → close. Composes /code-review, /clean-code-review, /forge-quench, and /test-sweep around the forgebug tool surface so a fix never closes without a regression check.
forge-troubleshoot
Diagnose and resolve Plan Forge issues — failed runs, broken validation gates, misconfigured environments, stalled slices, and orchestrator errors. Use when a plan run fails or the forge behaves unexpectedly.
security-audit
Comprehensive .NET security audit — OWASP vulnerability scan, NuGet vulnerability check, secrets detection, and combined severity report.
api-doc-gen
Generate or update OpenAPI specification from .NET controller attributes. Validate spec-to-code consistency. Use after adding or changing API endpoints.
audit-loop
Run a recursive audit drain loop — discover findings from the running system, triage each into bug/spec/classifier lanes, repeat until convergence. USE FOR: end-to-end audit of a deployed or locally-running app, draining findings to zero. DO NOT USE FOR: single-shot tempering runs (use forgetemperingrun), one-off bug…