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 skills add andregusman-raiz/a-gusman-claude --skill ag-pipeline-issuegit clone --depth 1 https://github.com/andregusman-raiz/a-gusman-claudeWrote 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/skills/andregusman-raiz/a-gusman-claude/ag-pipeline-issue)<a href="https://agentmods.dev/skills/andregusman-raiz/a-gusman-claude/ag-pipeline-issue"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-pipeline-issue/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/andregusman-raiz/a-gusman-claude/ag-pipeline-issue"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-pipeline-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00051 | $0.02666 |
| Opus 5.5 | $0.00020 | $0.01066 |
| Sonnet 5.5 | $0.00010 | $0.00533 |
| Haiku 4.5 | $0.00005 | $0.00267 |
Grade A, and why
ag-pipeline-issue 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 1mo 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 — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ag-pipeline-issue — Issue Pipeline
Pipeline obrigatorio para trabalho baseado em GitHub Issues. Garante que toda issue tem SPEC, toda implementacao e verificada contra a SPEC, e toda entrega e testada.
Invocation
Use the Agent tool with:
subagent_type:ag-pipeline-issuemode:autorun_in_background:falseprompt: Compose from template below + $ARGUMENTS
NOTE: NOT background — orchestrator needs to coordinate sequential steps.
Prompt Template
Issue: [issue number, URL, ou descricao]
Repo: [owner/repo — detectar via git remote se nao fornecido]
Projeto path: [CWD or user-provided path]
Executar pipeline completo: Fetch Issue → SPEC → Plan → Build → Verify → Test → Close.
Seguir TODAS as fases sequencialmente. NUNCA pular fase.
Pipeline: 7 Fases
Fase 0: Fetch Issue
Carregar contexto completo da issue do GitHub.
gh issue view [number] --json title,body,labels,assignees,comments
Extrair:
- Titulo: o que resolver
- Body: contexto, criterios de aceitacao, screenshots
- Labels: classificacao (bug, feature, tech-debt, security, etc)
- Comentarios: contexto adicional, discussoes
Se a issue nao tem criterios de aceitacao claros:
- Inferir do contexto e documentar na SPEC
- Marcar como
[INFERRED]para review do usuario
Fase 1: SPEC (ag-especificar-solucao)
Criar SPEC tecnica baseada na issue. Spawnar ag-especificar-solucao:
Agent({
subagent_type: "ag-especificar-solucao",
mode: "auto",
run_in_background: false,
prompt: "Feature/Problema: [titulo + body da issue #N]
Escopo: [extraido da issue]
Issue ref: #[number]
Criar SPEC tecnica implementavel. A SPEC DEVE incluir:
1. Referencia a issue: GitHub Issue #[number]
2. Criterios de aceitacao (extraidos ou inferidos da issue)
3. Interface/comportamento esperado
4. Edge cases
5. O que NAO esta no escopo (OOS)
6. Checklist de verificacao (cada item verificavel independentemente)
Salvar em: docs/specs/issue-[number]-spec.md
Max 200 linhas."
})
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.
- 1mo ago First seen · 324 lines · 51 tokens per session scan A a3ebe4524a6c
ag-pipeline-issue is a skill published in the GitHub repository andregusman-raiz/a-gusman-claude (18 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 2,666 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
scaffold
Scaffold a new feature end-to-end in one pass — module, types, tests stub, docs stub, and registration — so the first commit isn't boilerplate drift. Automation-first; infers the project's conventions from neighbors. Use whenever the user wants to scaffold a feature, stub a module, or runs /scaffold, or before…
ds-build
Plan executor — take an issue, a specs/{feature}/tasks.md, or a plain request and implement it unit by unit with a verify signal per unit, red-proven tests, budgeted backtracking, and a code-proven close. Use when the plan exists and the work is to be done, not planned.
project-setup
Bootstrap new projects with strong typing, linting, formatting, and testing. Supports Python, TypeScript, and other languages with research fallback.
bmad-agent-dev
Senior software engineer for story execution and code implementation. Use when the user asks to talk to Amelia or requests the developer agent.
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…