Borrowing it
Nothing to install: this file belongs to manushi4/Screenhand. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/manushi4/Screenhand/main/.claude/agents/chaos.mdgit clone --depth 1 https://github.com/manushi4/ScreenhandWrote 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/manushi4/screenhand/chaos)<a href="https://agentmods.dev/agents/manushi4/screenhand/chaos"><img src="https://agentmods.dev/badge/agents/manushi4/screenhand/chaos/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/agents/manushi4/screenhand/chaos"><img src="https://agentmods.dev/badge/agents/manushi4/screenhand/chaos.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.00040 | $0.01558 |
| Opus 5.5 | $0.00016 | $0.00623 |
| Sonnet 5.5 | $0.00008 | $0.00312 |
| Haiku 4.5 | $0.00004 | $0.00156 |
Grade A, and why
Chaos 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 128 lines · 40 tokens per session scan A 3e87b3fe5e63
Chaos is an agent published in the GitHub repository manushi4/Screenhand (15 stars, last pushed 6mo ago), licensed AGPL-3.0. It adds 40 tokens to every session and 1,558 once invoked, about $0.0002 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-30.
Other agents, from other repositories
operator
An operator for carrying out explicitly requested tasks on a Windows computer through visible application actions. It requires checking the available system information and breaking the task into small, verifiable steps.
browser-recorder
Record browser interactions and generate test definitions. Use when: (1) By feature-verify skill after exploration to generate test YAML, (2) By test-authoring skill for assisted test creation, (3) By user for "record this flow" requests.
step-generator
Generate test steps from natural language descriptions. Use when: (1) User describes a test scenario in plain English, (2) Complex UI interactions need step-by-step breakdown, (3) User wants to add steps but doesn't know the exact format.
test-analyzer
Deep analysis of E2E test failures and results. Use when: (1) A test has failed and needs root cause analysis, (2) User wants to understand why a step failed, (3) Complex multi-step failures need investigation.
tests
Discovers tests, coverage config, and gaps. Executes nothing at T0. Higher tiers require host sandbox attestation in the contract.
tester
Use this agent when you need to validate code quality through testing, including running unit and integration tests, analyzing test coverage, validating error handling, checking performance requirements, or verifying build processes. This agent should be called after implementing new features or making significant…