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 skills/aretw0/agents-lab/project-intakenpx skills add aretw0/agents-lab --skill project-intakegit 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/project-intake)<a href="https://agentmods.dev/skills/aretw0/agents-lab/project-intake"><img src="https://agentmods.dev/badge/skills/aretw0/agents-lab/project-intake.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 | $0.00031 | $0.00302 |
| Opus 5 | $0.00015 | $0.00151 |
| Sonnet 5 | $0.00006 | $0.00060 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
project-intake 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 4d 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
Project intake skill
Use esta skill para começar trabalho produtivo em qualquer projeto, sem assumir stack específica.
Quando aplicar
- primeiro contato com repositório desconhecido;
- pedido amplo (“arruma isso”, “vamos começar”);
- risco de gastar tokens em diagnóstico longo sem ação.
Contrato mínimo de saída
Sempre entregar:
- perfil de projeto (
light-notes|app-medium|monorepo-heavy); - primeira fatia local-safe (título curto);
- validação focal;
- rollback explícito;
- recommendation/nextAction em linguagem curta.
Prompt de operação (resumido)
Classifique o projeto em leve/médio/pesado, proponha UMA primeira fatia local-safe,
defina gate focal e rollback, e mantenha saída curta (sem escopo protegido automático).
Anti-bloat
- Evite checklist longo se uma fatia simples já resolve o próximo passo.
- Evite plano de N etapas sem gate da etapa 1.
- Em dúvida entre duas trilhas, escolha a de menor blast radius e mais rápida de validar.
Hard stop
Se o próximo passo exigir CI/remote/publish/settings/protected scope, pare e peça foco explícito do operador.
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.
- 4d ago First seen · 44 lines · 31 tokens per session scan A f1cccfc70bc9
project-intake is a skill published in the GitHub repository aretw0/agents-lab (11 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 302 once invoked, about $0.0002 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 skills, from other repositories
mcp-scripting
Write mcpScript JavaScript for discovering, inspecting, and calling MCP tools.
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.
merge-upstream
Sync a fork branch with an upstream remote using a history-preserving merge. Use this whenever the user says /merge-upstream, merge upstream, sync upstream, sync fork, or wants upstream changes integrated without rebasing or force-pushing.
gpt-image-gen
MUST read before generating images. Detailed prompt-crafting guide for gpt-image models, covering tool routing (native imagegeneration server tool vs the generateimage tool), prompt structure from subject to background, verbatim text rendering, anti-patterns, and the revisedprompt feedback loop for iteration.
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.
pi-observability-local-dev
Use when developing or reviewing packages/pi-observability dashboard/server changes locally, especially rebuilding dist, restarting the 43190 server, validating UI behavior, or keeping the local dashboard in sync with source edits.