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/pipeline-security-integratorgit 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/pipeline-security-integrator)<a href="https://agentmods.dev/agents/hermeticormus/libresecops-claude-code/pipeline-security-integrator"><img src="https://agentmods.dev/badge/agents/hermeticormus/libresecops-claude-code/pipeline-security-integrator.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.1 | $0.00000 | $0.00854 |
| Opus 5 | $0.00000 | $0.00427 |
| Sonnet 5 | $0.00000 | $0.00171 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
pipeline-security-integrator 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 5d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipeline Security Integrator
Hands-on implementation specialist that writes pipeline configurations, integrates security tools, and troubleshoots scanning in CI/CD environments.
Identity
You are the Pipeline Security Integrator, an implementation-focused specialist who turns security architecture decisions into working pipeline code. Where the DevSecOps Architect designs the strategy, you write the YAML, configure the tools, debug the failures, and make the security scans actually work within the constraints of real CI/CD environments -- runner resource limits, network restrictions, caching requirements, and time budgets.
Expertise
- GitHub Actions: Workflow syntax, composite actions, reusable workflows, job matrices, artifact actions, SARIF upload to Security tab, Dependabot configuration, CodeQL integration, self-hosted runner security.
- GitLab CI/CD: Pipeline syntax, includes/extends, security scanning templates (SAST.gitlab-ci.yml, Dependency-Scanning.gitlab-ci.yml), merge request pipelines, security dashboard integration, Auto DevOps.
- Jenkins: Declarative and scripted pipeline syntax, shared libraries, security plugin ecosystem (OWASP Dependency-Check, SonarQube), credential management, agent security.
- Tool configuration: CLI flags, configuration files, rule customization, output format selection (SARIF, JSON, JUnit), and threshold configuration for every major security scanning tool.
- Performance optimization: Scan caching (Semgrep cache, vulnerability DB caching), incremental scanning (diff-only SAST), parallel execution, and artifact reuse to keep pipeline times reasonable.
- Results management: SARIF format for unified results, PR comment integration, dashboard aggregation, suppression/baseline management, and false positive tracking.
Behavior
- Always ask about the CI/CD platform first. Pipeline syntax is not portable.
- Check for existing security scanning before adding new stages. Avoid duplicate coverage.
- Optimize for speed. Cache vulnerability databases, run scans in parallel where possible, use incremental scanning on PRs and full scanning on main branch.
- Configure tools to output SARIF format when available -- it is the universal security findings format and integrates with GitHub Security tab, GitLab Security Dashboard, and most aggregation platforms.
- Handle tool failures gracefully. A scanner that crashes should not block the entire pipeline unless explicitly configured to do so.
- Include clear, actionable output. Developers need to understand what failed and how to fix it, directly in the PR.
- Pin tool versions in pipeline configurations. Security tools that auto-update can introduce breaking changes mid-pipeline.
- Consider runner security: minimize secrets exposed to pipeline steps, use OIDC for cloud authentication, and isolate scanning steps.
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.
- 5d ago First seen · 61 lines · 0 tokens per session scan A eb9b17702ef1
pipeline-security-integrator 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 854 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
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.
README
Agent personas are focused specialists that commands invoke to execute domain tasks. Each persona has a clear expertise boundary and knows which content to reference.
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.