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.
git clone --depth 1 https://github.com/tractorjuice/arckit-claudeWrote 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/commands/tractorjuice/arckit-claude/aws-research)<a href="https://agentmods.dev/commands/tractorjuice/arckit-claude/aws-research"><img src="https://agentmods.dev/badge/commands/tractorjuice/arckit-claude/aws-research/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/commands/tractorjuice/arckit-claude/aws-research"><img src="https://agentmods.dev/badge/commands/tractorjuice/arckit-claude/aws-research.svg" alt="Reviewed on agentmods" width="80" 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.00013 | $0.03175 |
| Opus 5.5 | $0.00005 | $0.01270 |
| Sonnet 5.5 | $0.00003 | $0.00635 |
| Haiku 4.5 | $0.00001 | $0.00317 |
Grade A, and why
aws-research 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 today.
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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- today Changed 9765eca4319a
- 25d ago Changed 2710d2f418f6
- 26d ago Changed · +1 lines 560c98886b74
- 28d ago Changed f433e0e63f1f
- 1mo ago First seen · 205 lines · 13 tokens per session scan A b89aa8e29975
aws-research is a command published in the GitHub repository tractorjuice/arckit-claude (6 stars, last pushed yesterday), with no licence file. It adds 13 tokens to every session and 3,175 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 commands, from other repositories
aws-research
Research AWS services and architecture patterns using AWS Knowledge MCP for authoritative guidance.
azure-research
Research Azure services and architecture patterns using Microsoft Learn MCP for authoritative guidance.
gcp-research
Research Google Cloud services and architecture patterns using Google Developer Knowledge MCP for authoritative guidance.
spec-release
Generate release notes, changelog, and deployment checklist.
well-architected
Six-pillar well-architected review with scores and improvement roadmap.
disaster-recovery
Design disaster recovery strategy with RTO/RPO targets, backup config, and incident runbooks.