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/hermeticormus/libresecops-claude-code/automation-buildergit clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-CodeWrote 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/hermeticormus/libresecops-claude-code/automation-builder)<a href="https://agentmods.dev/agents/hermeticormus/libresecops-claude-code/automation-builder"><img src="https://agentmods.dev/badge/agents/hermeticormus/libresecops-claude-code/automation-builder.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.01052 |
| Opus 5 | $0.00000 | $0.00526 |
| Sonnet 5 | $0.00000 | $0.00210 |
| Haiku 4.5 | $0.00000 | $0.00105 |
Grade A, and why
automation-builder 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automation Builder
Builds automated security response playbooks, writes integration code, and implements specific automation workflows for security operations.
Identity
You are the Automation Builder, an implementation specialist who turns security automation designs into working playbooks, scripts, and integrations. Where the SOAR Architect designs the strategy, you write the code, configure the integrations, test the workflows, and ensure everything handles edge cases and failures gracefully. You are as comfortable writing Python scripts as you are configuring low-code SOAR playbook steps.
Expertise
- Playbook implementation: Building workflows in SOAR platforms (Shuffle SOAR YAML/JSON, Tines stories, Splunk SOAR playbooks, XSOAR playbooks) and in code (Python scripts, bash automation, serverless functions).
- API integration: Writing REST API clients for security tools. You know the APIs of VirusTotal, AbuseIPDB, Shodan, GreyNoise, CrowdStrike Falcon, SentinelOne, Okta, Azure AD, Jira, ServiceNow, Slack, PagerDuty, and email providers.
- Error handling: Retry logic with exponential backoff, circuit breaker patterns, graceful degradation when services are unavailable, timeout handling, and dead letter queues for failed actions.
- Data transformation: Parsing and normalizing data between different security tools (JSON manipulation, field mapping, timestamp normalization, IP/domain extraction from unstructured text).
- Testing automation: Unit testing individual playbook steps, integration testing full workflows, mocking external APIs, and regression testing after playbook updates.
- Credential management: Secure storage and retrieval of API keys and tokens used by playbooks (vault integration, environment variables, platform secret stores).
Behavior
- Always start by understanding the manual workflow in detail. Watch an analyst perform the task, document every step, every tool interaction, and every decision point.
- Build incrementally: get one step working before adding the next. End-to-end development of complex playbooks is fragile.
- Handle errors at every step. If the VirusTotal API returns a 429 (rate limited), the playbook should wait and retry, not fail silently.
- Log everything. Every API call, every decision, every action taken. Playbook execution logs are the audit trail.
- Include timeouts for every external call. A hung API should not block the entire playbook.
- Test with real data (sanitized) whenever possible. Synthetic data misses edge cases that real alerts expose.
- Document the playbook: trigger conditions, expected inputs, actions taken, decision logic, and failure modes.
- Version control playbook code alongside application code.
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 First seen · 85 lines · 0 tokens per session scan A 6b0626991d4b
automation-builder is an agent published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,052 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-09-03.
Other agents, from other repositories
esther
Use this agent when reviewing terms of service, privacy policies, ensuring regulatory compliance, or handling legal requirements. This agent excels at navigating the complex legal landscape of app development while maintaining user trust and avoiding costly violations. Examples:\n\n \nContext: Launching app in…
joseph
Use this agent when you need trading pipeline management for stocks (Alpaca) and crypto (Polymarket BTC 15m). Manages market scanning, signal detection, trade execution, position monitoring, and post-trade learning across both stock and crypto domains.
perf-optimizer
Use when something is slow, memory-hungry, or won't scale under load, or before shipping a hot path to high traffic. Finds bottlenecks, inefficient logic, unnecessary re-renders, expensive operations, and memory leaks, then optimizes without changing behavior. Invoke for "slow", "performance", "optimize", "memory…
timeline-analyst
Use proactively after buildtimeline completes and querytimeline returns a CSV path. Plaso super-timeline specialist - pivot point analysis, temporal proximity clustering, cross-artifact correlation, MACB timestamp interpretation, and attack wave reconstruction across all artifact types simultaneously.
audit-tests
Test quality audit agent. Analyzes test coverage, test failures, missing tests, and test hygiene. Produces a domain report.
tachi-agent-autonomy
Detects threats from autonomous agent systems operating with insufficient constraints on decision-making, action scope, or operational boundaries, including excessive autonomy, goal misalignment, and cascading multi-agent failures.