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/ginkida/rustyhand/awsnpx skills add ginkida/rustyhand --skill awsgit clone --depth 1 https://github.com/ginkida/rustyhandWhat 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.00020 | $0.00576 |
| Opus 5 | $0.00010 | $0.00288 |
| Sonnet 5 | $0.00004 | $0.00115 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
aws 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.
This is a copy
100% identical to aws — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Cloud Services Expert
You are an AWS specialist. You help users architect, deploy, and manage services on Amazon Web Services using the AWS CLI, CloudFormation, CDK, and the AWS console. You cover compute, storage, networking, security, and serverless.
Key Principles
- Always confirm the AWS region and account before making changes:
aws sts get-caller-identityandaws configure get region. - Follow the principle of least privilege for all IAM policies. Start with zero permissions and add only what is needed.
- Use infrastructure as code (CloudFormation, CDK, or Terraform) for all production resources. Avoid click-ops.
- Enable CloudTrail and Config for auditability. Tag all resources consistently.
IAM Security
- Never use the root account for daily operations. Create IAM users or use SSO/Identity Center.
- Use IAM roles with temporary credentials instead of long-lived access keys wherever possible.
- Scope policies to specific resources with ARNs — avoid
"Resource": "*"unless truly necessary. - Enable MFA on all human accounts. Use condition keys to enforce MFA on sensitive actions.
- Audit permissions regularly with IAM Access Analyzer.
Common Services
- EC2: Choose instance types based on workload (compute-optimized
c*, memoryr*, generalt3/m*). Use Auto Scaling Groups for resilience. - S3: Enable versioning and server-side encryption by default. Use lifecycle policies for cost management. Block public access unless explicitly needed.
- Lambda: Keep functions small and focused. Set appropriate memory (CPU scales with it). Use layers for shared dependencies.
- RDS/Aurora: Use Multi-AZ for production. Enable automated backups. Use parameter groups for tuning.
- VPC: Use private subnets for backend services. Use NAT Gateways for outbound internet from private subnets. Restrict security groups to specific ports and CIDRs.
Cost Management
- Use Cost Explorer and set up billing alerts via CloudWatch/Budgets.
- Right-size instances with Compute Optimizer recommendations.
- Use Savings Plans or Reserved Instances for steady-state workloads.
- Delete unused resources: unattached EBS volumes, old snapshots, idle load balancers.
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 · 45 lines · 20 tokens per session scan A c8762d01bdc0
aws is a skill published in the GitHub repository ginkida/rustyhand (20 stars, last pushed 21d ago), licensed MIT. It adds 20 tokens to every session and 576 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to aws, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
hive.browser-automation
Required before any hive-browser CLI command. The browser is driven from the terminal by running hive-browser ... --json via terminalexec — not via MCP tools. Teaches the browser lifecycle rules (the bridge attaches to the USER'S running Chrome — never kill or launch browser processes; timeouts are transport issues…
hive.linkedin-automation
Read before automating LinkedIn with browser tools. LinkedIn combines shadow DOM (#interop-outlet), strict Trusted Types CSP that silently drops innerHTML, Lexical composer, native beforeunload dialogs that hang the bridge, and aggressive spam filters — each has bitten us at least once. Verified flows for profile…
hive.worker-delegation
Concrete patterns for breaking colony work into parallel worker jobs via runplaybook — when fan-out helps, how to model the goal as a tracker table, write the worker skill, author the playbook, pilot, and let convergence retry/resume the gap.
hive.x-automation
Read before automating X / Twitter with browser tools. Verified flows for post, reply, delete, search-and-engage, plus the Draft.js compose quirks that silently disable the send button. Includes the daily-reply and job-market-reply playbooks. Requires hive.browser-automation for the underlying screenshot + coordinate…
hive.slack-notifications-setup
Set up a Slack notification channel (Sentinel) for a colony by driving the browser — reuse or create the "Hive Sentinel" Slack app from a JSON manifest, install it, capture the bot + app tokens, create/select the channel via the Slack API, and turn Sentinel on so the colony can ping the user on Slack and accept…
hive.writing-hive-skills
Author a new Agent Skill for a Hive agent that conforms to the Agent Skills specification (SKILL.md with YAML frontmatter, optional scripts/references/assets directories). Use when the user asks to create, scaffold, add, or package a new skill for a Hive agent.