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/laurigates/claude-plugins/cigit clone --depth 1 https://github.com/laurigates/claude-pluginsWhat 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.00051 | $0.01456 |
| Opus 5 | $0.00026 | $0.00728 |
| Sonnet 5 | $0.00010 | $0.00291 |
| Haiku 4.5 | $0.00005 | $0.00146 |
Grade A, and why
ci 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 2d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Agent
Scaffold a complete CI/CD setup — multiple GitHub Actions workflows and deployment automation — in one isolated pass.
When to delegate to this agent
Reach for this agent to scaffold a complete CI/CD setup from scratch — several workflows (test, build, release, deploy) generated together in one isolated buildout. For a single-workflow edit or a one-file tweak, edit .github/workflows/ directly in the main session: spawning a subagent for a surgical change costs more context than it saves. (Usage telemetry through 2026-06 showed CI work is almost always small inline edits — 175 inline workflow edits vs zero agent dispatches over 37 days — which is why this agent is scoped to the full-buildout case rather than general "configure CI" work.)
Tool Selection
The harness blocks several common bash idioms — use the dedicated tool instead. These rules track measurable friction in agent threads (issue #1109); following them keeps the run fast and avoids hook-block round-trips.
| Avoid | Use instead |
|---|---|
find . -name '*.ts' |
Glob(pattern="**/*.ts") |
grep -r 'foo' src/ |
Grep(pattern="foo", path="src", -r=true) |
cat/head/tail on a file |
Read — use offset/limit to page through |
echo ... > file / cat > file |
Write(file_path=..., content=...) |
git add . / git add -A |
git add <explicit-paths> — protects unrelated coworker changes |
git add ... && git commit ... |
Two separate Bash calls — git's index.lock does not survive && |
Read before Edit/Write. The harness tracks read-state per agent thread. Read every file in the current thread before editing or writing it — the parent session's Read does not count. If a formatter, linter, or hook may have rewritten a file since you read it, Read again before the next Edit.
Scope
- Input: CI/CD requirement (test on PR, deploy on merge, etc.)
- Output: Pipeline configuration files
- Steps: 5-10, focused configuration
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.
- 2d ago First seen · 167 lines · 51 tokens per session scan A 3d3cd3a5312e
ci is an agent published in the GitHub repository laurigates/claude-plugins (54 stars, last pushed 2d ago), licensed MIT. It adds 51 tokens to every session and 1,456 once invoked, about $0.0003 per session on Opus 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
test-generator
Test generator for Shopware 6 tests. Execution environment for test generation skills — do not invoke directly. Skills fork into this agent via context: fork. Does not review tests — use the appropriate reviewer agent for that.
code-reviewer
Code review, documentation quality, security audit, and quality assurance specialist with structured reasoning and semantic code analysis.
quant-backtest-validator
Validates backtesting execution realism, transaction costs, and market microstructure modeling.
interactive-element-creator
Implements interactive JavaScript components for presentations (tabs, accordions, charts).
industry-terms-agent
Reviews articles for industry terminology compliance including acronyms, product names, and technical terms.
style-guide-generator
Analyzes published blog articles to extract consistent editorial patterns and generate comprehensive style guides.