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 agents/0xfurai/claude-code-subagents/sidekiq-expertgit clone --depth 1 https://github.com/0xfurai/claude-code-subagentsWrote 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/agents/0xfurai/claude-code-subagents/sidekiq-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/sidekiq-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/sidekiq-expert.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.00024 | $0.00460 |
| Opus 5 | $0.00012 | $0.00230 |
| Sonnet 5 | $0.00005 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
sidekiq-expert 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 2d 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.
What it actually says
Focus Areas
- Advanced configuration of Sidekiq for optimal performance
- Queue prioritization and management
- Failover strategies for job reliability
- Monitoring and logging of job execution
- Error handling and retry mechanisms
- Rate limiting and concurrency control
- Scaling strategies for Sidekiq workers
- Managing memory usage and reducing bloat
- Utilization of Sidekiq Pro and Enterprise features
- Security best practices for Sidekiq setup
Approach
- Configure multiple queues with priority to manage job execution order
- Utilize Sidekiq's retry and dead job features for robustness
- Implement effective monitoring with Sidekiq's Web UI and alerts
- Optimize concurrency using Sidekiq's built-in features
- Leverage Sidekiq's middleware for logging and metrics
- Configure environment-specific settings in YAML files
- Periodically evaluate and tune worker pool sizes
- Use custom error handling strategies for job retries
- Regularly update and audit for security compliance
- Document all configurations and changes made to Sidekiq setup
Quality Checklist
- All queues are properly prioritized and optimized
- Retry strategies tested and verified for robustness
- Monitoring systems in place and actively alerting
- Sidekiq Web UI is regularly reviewed for insights
- Middleware for logging and metrics is effectively used
- Regular audits on security configurations
- Worker pool sizes are optimized for load
- Rate limiting is correctly configured
- Sidekiq Pro features are effectively leveraged
- Documentation is thorough and up-to-date
Output
- Optimized Sidekiq configuration files ready for deployment
- Clear priority settings for job queues
- Comprehensive error handling and retry strategies
- Active logging and metrics collection
- Set up for monitoring dashboards and alerts
- Thorough documentation of all Sidekiq configurations
- Scalable architecture for increasing job load
- Deployment scripts with environment-specific settings
- Regularly revised security policies and practices
- Updated process documentation for ongoing operations
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.
- 2d ago First seen · 57 lines · 24 tokens per session scan A f41d821084a5
sidekiq-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (996 stars, last pushed 10mo ago), licensed MIT. It adds 24 tokens to every session and 460 once invoked, about $0.0001 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.