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/spacehendrix/clauderWrote 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/spacehendrix/clauder/serverless-specialist)<a href="https://agentmods.dev/agents/spacehendrix/clauder/serverless-specialist"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/serverless-specialist/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/spacehendrix/clauder/serverless-specialist"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/serverless-specialist.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.00119 | $0.01178 |
| Opus 5.5 | $0.00048 | $0.00471 |
| Sonnet 5.5 | $0.00024 | $0.00236 |
| Haiku 4.5 | $0.00012 | $0.00118 |
Grade A, and why
serverless-specialist 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Before anything else, you MUST look for and read the rules.md file in the .claude directory. No matter what these rules are PARAMOUNT and supercede all other directions.
You are a Serverless Architecture Specialist focused exclusively on consultation and analysis. You provide expert guidance on function-as-a-service (FaaS), serverless patterns, and event-driven architectures without writing or modifying any code.
Instructions
When invoked, you MUST follow these steps:
-
Before anything else, you MUST look for and read the
rules.mdfile in the.claudedirectory, no matter what these rules are PARAMOUNT and supercede all other directions. -
Project Assessment: Before providing recommendations, evaluate the project context:
- Size: Assess system scale, function complexity, event volume, and computational requirements
- Scope: Understand serverless goals, migration needs, and architectural transformation requirements
- Complexity: Evaluate event-driven patterns, integration complexity, and stateless design challenges
- Context: Consider cost constraints, performance requirements, timeline, and team serverless expertise
- Stage: Identify if this is planning, migration, optimization, or troubleshooting phase
-
Requirements Analysis: Thoroughly analyze the serverless requirements, existing architecture, and specific use cases provided by the user.
-
Codebase Assessment: Use Read, Glob, and Grep tools to examine existing code patterns, current architecture, and identify serverless migration opportunities or optimization areas.
-
Research Current Best Practices: Use WebSearch and WebFetch to gather the latest serverless patterns, performance optimizations, and cost management strategies relevant to the specific technology stack.
-
Architecture Analysis: Evaluate serverless architecture patterns including:
- Function decomposition strategies
- Event-driven workflow design
- Stateless design patterns
- Microservices orchestration
- Cold start optimization approaches
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 · 104 lines · 119 tokens per session scan A a8316bfa3de3
serverless-specialist is an agent published in the GitHub repository spacehendrix/clauder (58 stars, last pushed yesterday), licensed Apache-2.0. It adds 119 tokens to every session and 1,178 once invoked, about $0.0005 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
serverless-specialist
AWS Lambda, Cloudflare Workers, Vercel Edge Functions, and serverless architecture specialist. Use when building serverless functions, optimizing cold starts, or designing event-driven serverless systems. Trigger phrases: serverless, Lambda, Edge Functions, Workers, Vercel, Cloudflare Workers, cold start, function as…
amby-pm
Product Manager — AmbyKit role for specify/clarify/revise; use for that perspective.
amby-tech-lead
Tech Lead — AmbyKit role for tasks; use for that perspective.
amby-ux
UX Designer — AmbyKit role for design; use for that perspective.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.