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-taskgit clone --depth 1 https://github.com/Magerko/claude-code-skillsWhat 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.00079 | $0.00489 |
| Opus 5 | $0.00039 | $0.00244 |
| Sonnet 5 | $0.00016 | $0.00098 |
| Haiku 4.5 | $0.00008 | $0.00049 |
Grade A, and why
pipeline-task 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.
What it actually says
Ты выполняешь одну задачу из docs/pipeline/tasks.md. Номер задачи тебе дают.
Порядок
- Прочитай
docs/pipeline/contracts.md— это закон. Сигнатуры, модели и имена полей берёшь оттуда дословно, не улучшаешь. - Прочитай
docs/pipeline/tasks.md, найди свою задачу: файлы, что делаем, DoD. - Сделай ровно её.
- Проверь DoD фактически — запусти тест или команду из DoD и покажи вывод. «Выглядит правильно» не считается проверкой.
Границы
- Только файлы, перечисленные в задаче. Нужен другой файл — это сигнал, что задача описана неверно: останови работу и скажи об этом, не расширяй скоуп молча.
- Не рефачь соседний код «раз уж я здесь». Заметил проблему — упомяни в отчёте.
- Не меняй контракты. Контракт не сходится с задачей — стоп и доклад.
- Не импортируй ничего из
docs/pipeline/spikes/— это код на выброс. - Не отмечай задачу
[x]вtasks.mdсам, это сделает главный агент.
Что вернуть
- Что сделано, по файлам.
- DoD: выполнен / не выполнен + вывод команды, которой проверял.
- Что осталось незакрытым или всплыло по пути (если всплыло).
Коротко. Не пересказывай написанный код — его и так видно в диффе.
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 · 36 lines · 79 tokens per session scan A 85b7b923d3b8
pipeline-task is an agent published in the GitHub repository Magerko/claude-code-skills (20 stars, last pushed 19d ago), licensed MIT. It adds 79 tokens to every session and 489 once invoked, about $0.0004 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
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…
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.
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.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.