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 aretw0/agents-lab --skill stack-feedbackgit clone --depth 1 https://github.com/aretw0/agents-labWrote 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/aretw0/agents-lab/stack-feedback)<a href="https://agentmods.dev/skills/aretw0/agents-lab/stack-feedback"><img src="https://agentmods.dev/badge/skills/aretw0/agents-lab/stack-feedback/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/aretw0/agents-lab/stack-feedback"><img src="https://agentmods.dev/badge/skills/aretw0/agents-lab/stack-feedback.svg" alt="Reviewed on agentmods" width="80" 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.00039 | $0.00476 |
| Opus 5.5 | $0.00016 | $0.00190 |
| Sonnet 5.5 | $0.00008 | $0.00095 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
stack-feedback 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.
What it actually says
Feedback da Stack
Coleta feedback estruturado sobre o uso da stack @aretw0/pi-stack para orientar a curadoria e priorização do agents-lab.
Quando Usar
- O usuário encontrou um problema com a stack
- O usuário tem uma sugestão de melhoria
- O usuário descobriu um overlap ou conflito entre extensões
- O usuário quer sugerir uma nova extensão ou skill
Formato
Colete as seguintes informações:
Tipo
- 🐛 Bug — algo quebrado ou com comportamento inesperado
- 💡 Sugestão — melhoria ou nova feature
- 🔄 Overlap — duas extensões/skills fazendo a mesma coisa
- 📝 Descoberta — padrão, workaround ou insight útil
Contexto
- Qual pacote/skill/extensão é afetado?
- Qual terminal e sistema operacional?
- Qual provider e modelo?
Descrição
O que aconteceu, o que era esperado, o que foi observado.
Reprodução (se bug)
Passos mínimos para reproduzir.
Destino
Após coletar o feedback:
-
Verificar se já existe issue no repositório:
gh issue list --repo aretw0/agents-lab --json number,title --jq '.[] | "\(.number): \(.title)"' -
Se não existe, criar:
gh issue create --repo aretw0/agents-lab \ --title "[tipo] descrição curta" \ --body "conteúdo estruturado" -
Se é overlap, referenciar as duas partes conflitantes.
Qualidade do Feedback
O feedback deve ser:
- Específico — não "está estranho", mas "o monitor X não dispara quando Y"
- Reproduzível — passos claros, não "às vezes acontece"
- Contextualizado — terminal, OS, provider, modelo
- Construtivo — problema + sugestão quando possível
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 · 70 lines · 39 tokens per session scan A 96020086bd5e
stack-feedback is a skill published in the GitHub repository aretw0/agents-lab (11 stars, last pushed 3mo ago), licensed MIT. It adds 39 tokens to every session and 476 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-08-30.
Other skills, from other repositories
mcp-scripting
Read before writing mcpScript code. Covers tool discovery, the shape of call results (including JSON returned as text), and script limits.
gpt-image-gen
MUST read before generating images. Prompt-crafting guide for gpt-image-2.5 covering tool routing (native imagegeneration server tool vs the generateimage tool), model and quality selection, prompt structure, exact text rendering, reference-image editing, transparent assets, output formats, and multi-turn refinement.
tmux-manual-qa
Run a single manual tmux-based QA scenario for the todo continuation feature against the real CLI (./pi-test.sh) in an interactive TUI. Captures scrollback, asserts deterministic pass/fail count markers, and cleans up test fixtures. Use only for the manual-qa milestone features.
release-notes
Write release notes for a tagged release — a business-impact summary of what changed for the user, plus a thanks section naming every contributor whose commits are in the release. Short by construction.
review-this-branch
Run the nohuman review gate (fresh-session adversarial reviewer + tamper guard) over the current branch or a GitHub pull request, with no server, no database, and no onboarding, and relay the pass/fail checklist.
pi-package-sandbox-test
Use when verifying that published Pi packages install and load for normal users, including pi.dev package compatibility checks, release validation, Daytona sandbox tests, and package installability audits.