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/agentskit-io/agentskit-registry/application-patterns-wave-04git clone --depth 1 https://github.com/AgentsKit-io/agentskit-registryWrote 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/agentskit-io/agentskit-registry/application-patterns-wave-04)<a href="https://agentmods.dev/agents/agentskit-io/agentskit-registry/application-patterns-wave-04"><img src="https://agentmods.dev/badge/agents/agentskit-io/agentskit-registry/application-patterns-wave-04.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 | $0.00000 | $0.02593 |
| Opus 5 | $0.00000 | $0.01296 |
| Sonnet 5 | $0.00000 | $0.00519 |
| Haiku 4.5 | $0.00000 | $0.00259 |
Grade A, and why
application-patterns-wave-04 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Application patterns — Wave 04
Wave 04 focuses on engineering evidence, data quality, security operations, content verification, research synthesis, product decisions, and revenue handoffs. Every pattern below uses synthetic input and is a starting point for inspection, not evidence of customer impact, security posture, compliance, financial performance, or production readiness.
Shared run contract
npx agentskit add <agent-id>
npm test -- --run registry/<agent-id>/agent.test.ts
Use a configured adapter or the credential-free demo path where supported. Inspect the typed result, evidence references, missing context, and review requirement. Never treat a generated result as a deployment, security response, audit conclusion, publication, forecast, prioritization, or release decision.
Engineering, data, and platform reliability
API Contract Reviewer — breaking change map
- Agent: coding-api-contract-reviewer
- Try: Compare two synthetic API schemas and return breaking changes, non-breaking changes, affected consumers, missing context, and verification steps.
- Inspect: exact diff evidence, consumer assumptions, severity rationale, and separation between review findings and implementation authority.
- Next contribution: add a fixture where a changed default is breaking for one consumer but safe for another.
- Human boundary: maintainers decide compatibility policy, migration work, and release timing.
Performance Interpreter — measurements before diagnosis
- Agent: coding-performance-interpreter
- Try: Interpret synthetic Lighthouse and bundle reports into observed measurements, candidate bottlenecks, confidence, and proposed verification commands.
- Inspect: metric fidelity, source references, correlation versus causation, and missing runtime context.
- Next contribution: add a fixture where a large asset is not the measured bottleneck and should not be over-prioritized.
- Human boundary: engineers validate performance changes on representative environments before shipping.
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.
- 3d ago First seen · 177 lines · 0 tokens per session scan A 548eed81188a
application-patterns-wave-04 is an agent published in the GitHub repository AgentsKit-io/agentskit-registry (5 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,593 tokens. 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 agents, from other repositories
chaos-monkey
You are the Chaos Monkey ("Kaos Maymunu") — a mutation-testing saboteur for the WrongStack fleet. Your job is to prove whether a test suite actually pins down the code it claims to cover, by deliberately breaking that code and watching which mutants survive.
explore-companion
You are the Explore Companion. Your job is to make the leader faster, not to lead. The leader is already executing the main task; you run behind it, answer one narrow probe, and hand back just enough map that the leader does not spend its own context discovering where things are.
memory-curator
Agent "memory-curator" from WrongStack/WrongStack, covering core responsibilities and output.
android
Agent "android" from WrongStack/WrongStack, covering working rules and output.
backend
You are the Backend agent. Your job is server-side logic: services, business rules, persistence wiring, and reliable request handling.
compliance
You are the Compliance agent. Your job is license, privacy, and regulatory review: check dependency licenses, data-handling, and control coverage against GDPR/SOC2-style requirements.