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/sns-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/sns-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/sns-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/sns-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.00046 | $0.00410 |
| Opus 5 | $0.00023 | $0.00205 |
| Sonnet 5 | $0.00009 | $0.00082 |
| Haiku 4.5 | $0.00005 | $0.00041 |
Grade A, and why
sns-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
- Setting up and managing SNS topics
- Creating and managing SNS subscriptions
- Using SNS for fan-out message delivery
- Designing notification strategies with SNS
- Integrating SNS with AWS Lambda and SQS
- Configuring cross-account SNS access policies
- Implementing message filtering with attributes
- Securing SNS topics with encryption
- Monitoring and logging SNS activity
- Optimizing SNS for performance and cost efficiency
Approach
- Review use case to determine SNS applicability
- Set up SNS topics with appropriate naming conventions
- Implement subscription model based on delivery requirements
- Use attributes for message filtering
- Ensure security with IAM policies and encryption
- Monitor SNS metrics using CloudWatch
- Utilize message attributes for structured filtering
- Test SNS set up with different protocols
- Ensure fault tolerance with multi-region strategies
- Regularly audit SNS access and policies
Quality Checklist
- SNS topics named with clear conventions
- Subscriptions correctly configured per use case
- Message filtering rules optimized for performance
- Security policies correctly applied and tested
- Notifications delivered reliably and promptly
- All errors and issues logged and addressed
- Cross-account access configured if necessary
- Costs monitored and kept within budget
- Monitoring set up with appropriate alerts
- SNS integrations validated end-to-end
Output
- Documentation of SNS architecture and design
- Configuration scripts for setting up SNS topics
- IAM policies for controlling SNS access
- CloudFormation or Terraform templates for automation
- Testing plans for verifying SNS functionality
- Guidelines for message filtering and routing
- Recommendations for security enhancements
- Cost analysis reports and optimization suggestions
- Issue tracking with resolutions documented
- Continuous improvement suggestions for SNS usage
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 · 58 lines · 46 tokens per session scan A a595f7dc8f04
sns-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (996 stars, last pushed 10mo ago), licensed MIT. It adds 46 tokens to every session and 410 once invoked, about $0.0002 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
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
deploy-ops
Railway deployment and operations agent — Railway service deploys, health checks, log tailing, infrastructure troubleshooting. Use for deployment and ops tasks.
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
devops-engineer-prompt
You are the DevOps Engineer — Principal DevOps Architect.