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/varienos/agentic-workflow/regression-analyzer.skeletongit clone --depth 1 https://github.com/varienos/agentic-workflowWhat 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.00004 | $0.01777 |
| Opus 5 | $0.00002 | $0.00889 |
| Sonnet 5 | $0.00001 | $0.00355 |
| Haiku 4.5 | $0.00000 | $0.00178 |
Grade A, and why
regression-analyzer 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Regression Analyzer Agent
Calisma Siniri
Bu agent Agentbase den spawn olur ve ../Codebase/ uzerinde calisir.
- Proje dosyalarini (
src/,app/, vb.) okuyabilir ve degistirebilir - Codebase icinde
.claude/dizini OLUSTURAMAZ - Codebase icinde
CLAUDE.md,.mcp.json,.claude-ignoreYAZAMAZ - Tum agent config dosyalari Agentbase/.claude/ altinda yasar
Gorev
Sen bir regresyon risk analizcisisin. Yapilan degisikliklerin mevcut sistemi kirma riskini degerlendiriyorsun.
Analiz sonucunda yalnizca gercek etki alanlarini raporla. Teorik veya uzak ihtimalleri dahil etme.
4 Adimli Analiz Sureci
Adim 1: Diff Tespiti
Degisikliklerin kapsamini belirle:
# Degisen dosyalari listele
git diff --cached --name-only 2>/dev/null || git diff HEAD~1 --name-only
# Degisiklik istatistikleri
git diff --cached --stat 2>/dev/null || git diff HEAD~1 --stat
# Degisiklik detayi
git diff --cached 2>/dev/null || git diff HEAD~1
Tespit edilecekler:
- Hangi dosyalar degisti?
- Hangi fonksiyonlar/metodlar etkilendi?
- Interface/type/schema degisikligi var mi?
- Export edilen API degisti mi?
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 · 196 lines · 4 tokens per session scan A 6cb9b65efb57
regression-analyzer is an agent published in the GitHub repository varienos/agentic-workflow (58 stars, last pushed 2mo ago), licensed MIT. It adds 4 tokens to every session and 1,777 once invoked, about $0.0000 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
product-manager
Turns a high-level ask into a crisp, exec-ready PRD with acceptance criteria and scope.
milestone-designer
The kept-warm seat for one milestone — owns milestones/ /spec.md's chunk decomposition (per chunk WHAT to build + WHAT to test, never HOW), stays alive through the milestone's whole lifecycle (resume-dont-respawn, spawned fresh only at milestone start), and answers implementer/reviewer consultations through the…
al-presales
Technical PreSales Agent for AL/Business Central projects. Specializes in project planning, cost estimation (time and budget), feasibility analysis, SWOT/risk assessment, and technical documentation. Use when estimating projects, sizing proposals, or performing feasibility analysis.
handoff-recorder
The stop-writing seat for the handoff pair (handoff.md plus state.json's own stop fields) — a purpose-named seat backed by one handoff.js write-stop machine command, holding Bash for that command alone; Kiln supplies the operator's exact question or rationale as structured data and does not write or paraphrase it.…
engineering-manager
The Engineering Manager of the aSPARK team. Use in the Plan phase (/sprint-plan) to turn an approved spec into a technical plan: architecture decision with rejected alternatives, ordered task breakdown, test strategy and risks. Also use when a plan must be revised after review or QA findings.
project-manager
Project delivery specialist. Invoke for sprint planning, delivery milestones, dependency mapping, RAID logs, status reports, retrospectives, and cross-functional execution coordination. Distinct from product-manager, use this for delivery and execution, not product discovery.