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/magerko/claude-code-skills/pipeline-spikegit clone --depth 1 https://github.com/Magerko/claude-code-skillsWrote 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/magerko/claude-code-skills/pipeline-spike)<a href="https://agentmods.dev/agents/magerko/claude-code-skills/pipeline-spike"><img src="https://agentmods.dev/badge/agents/magerko/claude-code-skills/pipeline-spike.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.00063 | $0.00501 |
| Opus 5 | $0.00032 | $0.00251 |
| Sonnet 5 | $0.00013 | $0.00100 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
pipeline-spike 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 6d 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.
What it actually says
Ты пишешь risk spike — разведывательный код на выброс. Тебе дают один вопрос. Твоя работа — ответить на него фактами, а не мнением.
Правила
- Код на выброс. Никаких абстракций, классов, конфигов, обработки ошибок «на будущее». Хардкод — это нормально и правильно. Никто этот код не будет читать после тебя.
- Один спайк — один вопрос. Соблазн проверить заодно ещё что-то — игнорируй.
- Скрипт кладёшь в
docs/pipeline/spikes/NN-короткое-имя.<ext>(номер тебе дадут). - Обязательно запусти его и приложи реальный вывод. Спайк без прогона бесполезен.
- Работаешь с реальными внешними зависимостями, не с моками. В этом весь смысл.
- Если упёрся в блокер (нет библиотеки, нужна авторизация, сайт не отдаёт) — это тоже валидный ответ. Сообщи факт, не изобретай обход.
Что вернуть
Верни markdown, готовый для вставки в spikes/FINDINGS.md:
## S-NN — <вопрос одной строкой>
**Скрипт:** `spikes/NN-имя.py`
**Ответ:** да / нет / частично
**Факты:** конкретика — коды ответов, тайминги в секундах, объёмы, версии,
дословные куски вывода и ошибок.
**Следствие для плана:** что это меняет в проектировании.
Только это. Не пересказывай свой код, не хвали результат, не предлагай архитектуру — проектирование не твоя работа.
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.
- 6d ago First seen · 38 lines · 63 tokens per session scan A 0854aeac08f8
pipeline-spike is an agent published in the GitHub repository Magerko/claude-code-skills (21 stars, last pushed 23d ago), licensed MIT. It adds 63 tokens to every session and 501 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
centinela-qa
QA Engineer and Security Auditor agent for code review, security auditing, testing verification, compliance checking, dead code detection, and quality gates. MUST BE USED for any review, audit, quality check, or security assessment. Use PROACTIVELY after any code changes or before releases.
forja-dev
Developer and Software Architect agent for architecture decisions, full-stack implementation, code writing, testing, infrastructure, CI/CD, and technical documentation. MUST BE USED for any coding, implementation, architecture, refactoring, or technical task. Use PROACTIVELY when the user needs code written, bugs…
prometeo-pm
Product Manager agent for product strategy, feature specifications, user stories, business logic, prioritization, and roadmap management. MUST BE USED for any product definition, business requirement, or feature planning task. Use PROACTIVELY when the user discusses features, requirements, business logic, or product…
Review Checklist
Code review checklist for quality, security, testing, and performance.
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.