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 slbug/claude-ruby-grape-rails --skill async-patternsgit clone --depth 1 https://github.com/slbug/claude-ruby-grape-railsWrote 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/slbug/claude-ruby-grape-rails/async-patterns)<a href="https://agentmods.dev/skills/slbug/claude-ruby-grape-rails/async-patterns"><img src="https://agentmods.dev/badge/skills/slbug/claude-ruby-grape-rails/async-patterns/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/slbug/claude-ruby-grape-rails/async-patterns"><img src="https://agentmods.dev/badge/skills/slbug/claude-ruby-grape-rails/async-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 129 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 130 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 131 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00028 | $0.01943 |
| Opus 5.5 | $0.00011 | $0.00777 |
| Sonnet 5.5 | $0.00006 | $0.00389 |
| Haiku 4.5 | $0.00003 | $0.00194 |
Grade A, and why
rb:async-patterns 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 — 430 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Async Patterns
Fiber-based concurrency for Ruby using the async gem.
Overview
The async gem provides fiber-based concurrency:
| Approach | Use Case | Concurrency Model |
|---|---|---|
| Threads | CPU-bound work | OS threads |
| Async | I/O-bound work | Fibers (lightweight) |
| Processes | Isolation | Fork/spawn |
Use async when:
- Making many HTTP requests
- Reading from multiple files/streams
- Database queries that can run in parallel
- WebSocket handling
- High-concurrency I/O
Installation
# Gemfile
gem 'async'
gem 'async-http' # HTTP client
gem 'async-io' # I/O operations
gem 'falcon' # Async web server (optional)
# Rails integration
gem 'async-job' # Async job processor
gem 'async-cable' # Async Action Cable (optional)
Basic Async
Simple Task
require 'async'
Async do |task|
task.sleep(1)
puts "Done!"
end
Concurrent Operations
require 'async'
Async do |task|
# Spawn multiple concurrent tasks
tasks = []
tasks << task.async do
task.sleep(1)
"Task 1 done"
end
tasks << task.async do
task.sleep(0.5)
"Task 2 done"
end
tasks << task.async do
task.sleep(1.5)
"Task 3 done"
end
# Wait for all and get results
results = tasks.map(&:wait)
puts results
# Total time: ~1.5s (not 3s!)
end
Error Handling
Async do |task|
tasks = []
tasks << task.async do
raise "Task 1 failed"
end
tasks << task.async do
"Task 2 success"
end
results = tasks.map do |t|
begin
t.wait
rescue => e
{ error: e.message }
end
end
puts results
# => [{:error=>"Task 1 failed"}, "Task 2 success"]
end
Concurrent HTTP Requests
Using async-http
require 'async'
require 'async/http/internet'
Async do |task|
internet = Async::HTTP::Internet.new
# Fetch multiple URLs concurrently
responses = []
urls = [
'https://api.example.com/users',
'https://api.example.com/products',
'https://api.example.com/orders'
]
urls.each do |url|
responses << task.async do
response = internet.get(url)
[url, response.read]
end
end
# Wait for all responses
data = responses.map(&:wait)
# Process results
data.each do |url, body|
puts "#{url}: #{body.length} bytes"
end
internet.close
end
What ships with it
1 file 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.
- 1mo ago First seen · 430 lines · 28 tokens per session scan A 479a7abdcdfe
rb:async-patterns is a skill published in the GitHub repository slbug/claude-ruby-grape-rails (7 stars, last pushed 16d ago), licensed MIT. It adds 28 tokens to every session and 1,943 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
draper-decorators
This skill should be used when the user asks to "create a decorator", "write a decorator", "move logic into decorator", "clean logic out of the view", "isn't it decorator logic", "test a decorator", or mentions Draper, keeping views clean, or representation logic in decorators. Should also be used when editing…
rails-expert
Rails 7+ specialist that optimizes Active Record queries with includes/eagerload, implements Turbo Frames and Turbo Streams for partial page updates, configures Action Cable for WebSocket connections, sets up Sidekiq workers for background job processing, and writes comprehensive RSpec test suites. Use when building…
new
Create a new project to start development quickly.
pinme-email
Use this skill when a PinMe project (Worker TypeScript) needs to integrate email sending (sendemail). Guides AI to generate correct Worker TS code.
rails-conventions
Rootstrap Rails conventions. Use when writing, reviewing, or editing any Rails code — controllers, models, migrations, routes, views, mailers, initializers, locale files, or Rails config. Covers routing, ActiveRecord, migrations, i18n, time zones, mailers, assets, Bundler groups, and logging.
dotnet-backend
Build and upgrade ASP.NET Core services with typed contracts, dependency lifetimes and verified persistence. Use when implementing .NET APIs, background services or runtime migrations; coordinate SDK, target framework and package support.